Prior to #15302, we wanted to make sure the component had rendered the
hidden input when receiving the focus event. To do so, we added some
workarounds for scenarios where the focus event was triggered before the
component had the chance to detect it was attached or visible.
After that pull-request, however, we always render the hidden input
independently of which events the component has observed, thus making
those workarounds not necessary anymore.
Please, note that we decided not to include this commit's changes in
beta, and want to let them bake for a full release cycle instead.
Co-authored-by: sadick254 <sadickjunior@gmail.com>
Adds the npm_config_jobs env variable across build scripts that may benefit from it (ones that run apm install). This variable is used by node-gyp to compile native code with a number of threads equal to the reported CPU core count
Refactors the codes that were responsible for updating different parts of TextEditor out of update function, and, then, it uses those refactored functions directly, which bypasses the loop and switch case inside update.
`finishUpdate` is also refactored to allow finishing update of TextEditor from inside the update functions without the need for creating objects outside and passing them in.
* cleanup TodoElectronIssue for GCM initVector
* cleanup TodoElectronIssue drop manual set of random value for debugging-port
* Remove workaround for slow crypto.randomBytes
* produceCachedData --> script.createCachedData()
* Remove arguments from childProcess.removeAllListeners()
Co-authored-by: DeeDeeG <DeeDeeG@users.noreply.github.com>
macOS Gatekeeper adds a flag ("-psn_0_[six or seven digits here]") when it intercepts Atom launches.
This happens for fresh downloads, new installs, or first launches after upgrading).
We don't need this flag, and yargs interprets it as many short flags. So, we filter it out.
This allows loading the packages that are Es module and export their function wrapped in a default object. This is the case for any package that uses Babel 6, Babel 7, or other modern compilers for transpiling their package.
Based on the docs true is equal to {capture: true}
> In older versions of the DOM specification, the third parameter of addEventListener() was a Boolean value indicating whether or not to use capture. Over time, it became clear that more options were needed. Rather than adding more parameters to the function (complicating things enormously when dealing with optional values), the third parameter was changed to an object that can contain various properties defining the values of options to configure the process of removing the event listener.
https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners
