This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Commits on Jan 18, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 8dbd98a - Browse repository at this point
Copy the full SHA 8dbd98aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 84e352f - Browse repository at this point
Copy the full SHA 84e352fView commit details -
Update snapshot path from snapshot_blob to v8_context_snapshot
Related commit: electron/electron@3ac4c1f
Configuration menu - View commit details
-
Copy full SHA for 71bf72a - Browse repository at this point
Copy the full SHA 71bf72aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7e5ba7c - Browse repository at this point
Copy the full SHA 7e5ba7cView commit details -
Use new attributeStyleMap for elements
More info here: https://developers.google.com/web/updates/2018/03/cssom
Configuration menu - View commit details
-
Copy full SHA for 1276f6f - Browse repository at this point
Copy the full SHA 1276f6fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7399753 - Browse repository at this point
Copy the full SHA 7399753View commit details -
Configuration menu - View commit details
-
Copy full SHA for 89de78b - Browse repository at this point
Copy the full SHA 89de78bView commit details -
Configuration menu - View commit details
-
Copy full SHA for b692f0d - Browse repository at this point
Copy the full SHA b692f0dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 10dbd69 - Browse repository at this point
Copy the full SHA 10dbd69View commit details -
Make invalid JS file fail Babel spec again
This change uses a different JavaScript syntax to cause the "when a .js file does not start with 'use babel'" spec to fail again after upgrading to Electron 3 / Node 10.3.0. The previous generator syntax seems to be supported in the version of V8 used by Node 10 so we now need to use the 'export default' syntax to trigger an error. I've verified that changing the first line of this file to 'use babel' causes the file to load successfully, so it seems this new syntax is effective to verify the desired behavior.
Configuration menu - View commit details
-
Copy full SHA for 8eccaf2 - Browse repository at this point
Copy the full SHA 8eccaf2View commit details -
Configuration menu - View commit details
-
Copy full SHA for eee7ae8 - Browse repository at this point
Copy the full SHA eee7ae8View commit details -
Use correct fontWeight value in ThemeManager spec
In Chrome 66+ it seems that getComputedStyle().fontWeight returns the computed numeric value of the style instead of the original descriptive name. We now look for value '700' which corresponds to the value of 'bold'.
Configuration menu - View commit details
-
Copy full SHA for ff42923 - Browse repository at this point
Copy the full SHA ff42923View commit details -
Configuration menu - View commit details
-
Copy full SHA for f70be77 - Browse repository at this point
Copy the full SHA f70be77View commit details -
Remove listeners for specific events in Task class
This change is necessary for Electron 3 to a bug in Node.js 10.2.x which causes the `removeAllListeners` method to no longer remove all listeners for any event name when no argument is passed: nodejs/node#20924 This issue has been fixed in Node.js 10.3.0+ so we will have to remove this workaround when we move to Electron 4.0 to avoid future event handler leaks.
Configuration menu - View commit details
-
Copy full SHA for 7b7fd7b - Browse repository at this point
Copy the full SHA 7b7fd7bView commit details -
Configuration menu - View commit details
-
Copy full SHA for a41b69e - Browse repository at this point
Copy the full SHA a41b69eView commit details
Commits on Jan 22, 2019
-
Update StyleManager specs to address deprecated ::shadow selectors
As of Chromium 63, ::shadow CSS selectors have been fully removed: https://developers.google.com/web/updates/2017/10/remove-shadow-piercing As a result, any usage of ::shadow in a stylesheet seems to get removed as soon as the stylesheet is applied to an HTMLStyleElement. Since we have a couple of tests that expect ::shadow selectors to be present, we must remove those expectations since those selectors do not appear any longer.
Configuration menu - View commit details
-
Copy full SHA for 11ed913 - Browse repository at this point
Copy the full SHA 11ed913View commit details
Commits on Jan 26, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 7248737 - Browse repository at this point
Copy the full SHA 7248737View commit details -
Configuration menu - View commit details
-
Copy full SHA for b06da5d - Browse repository at this point
Copy the full SHA b06da5dView commit details
Commits on Jan 29, 2019
-
Configuration menu - View commit details
-
Copy full SHA for fdece6f - Browse repository at this point
Copy the full SHA fdece6fView commit details
Commits on Jan 30, 2019
-
Remove cached-run-in-this-context dependency
This dependency is no longer needed now that we use Node's built-in APIs
Configuration menu - View commit details
-
Copy full SHA for 6903be1 - Browse repository at this point
Copy the full SHA 6903be1View commit details
Commits on Feb 1, 2019
-
Configuration menu - View commit details
-
Copy full SHA for fec6856 - Browse repository at this point
Copy the full SHA fec6856View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3714a8d - Browse repository at this point
Copy the full SHA 3714a8dView commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.