Conversation
e49044e to
e0c9d75
Compare
63432bb to
1e47e17
Compare
|
Since Electron v1.4.1 ships with electron/electron#7209, I hope this PR will resolve #11692. |
4549b73 to
0b54c9d
Compare
0b54c9d to
fcddf83
Compare
|
Observations from around 10 minutes of light usage: NOTHING IS BLURRY ANYMORE!I have beautiful subpixel antialiasing on everything, even the actual code for the first time ever* 💥. Fixes #12652, maybe #7261, #3869, #2833. Scrollbars seem to disappear randomly. Haven't narrowed this down but I did notice one of my files didn't have a scrollbar. * Just noticed that the tabs and mini-editors don't have subpixel AA, but that's super minor compared to before. |
|
Ok, something else related to subpixel AA: |
Have this happening with the vertical scrollbar on the TextEditor active when restoring session. In the case of split panes (I tried left/right) both TextEditors are missing vertical scrollbars.
If you resize the pane so that the horizontal scrollbar appears or disappears then you can get the vertical scrollbar to appear, but in all other cases this file seems to be missing the vertical scrollbar. Tested with both Atom Light and One Dark themes. This does not reproduce in 1.11-beta5. Don't know about other dev versions. |
|
The disappearing scrollbar issue appears to happen on the first file that is opened/restored. From the dev tools, the scrollbar (and scrollbar corner) is being given a width of 10px instead of the usual 15px. If I change it to 15, then the scrollbar appears. Anything > 10 works. /cc @simurai Now, some more subpixel antialiasing updates. As I said before, it works for the most part. Here's when it fails:
Also, Atom occasionally crashes when I try to close it. I'm not sure if that is specific to the Electron upgrade though as it's happened before as well. |
|
More comments. I appear to lose subpixel antialiasing during any type of scrolling (programmatically through go-to-line or find-and-replace, for example, or manually) except for mousewheel scrolling. The dev tools are frozen after reloading the window and must be closed through the keybinding and reopened in order for it to work. |
|
Chrome tends to switch from sub-pixel to regular AA when it expects to need to redraw it several times such as in animation. This is because AA can be cached and re-used whereas sub-pixel depends on the horizontal offset. |
|
The scrollbar issue is super weird. Changing the It seems any property that triggers a layout reflow makes the scrollbar visibility alternate when changing the value: And just typing in search + replace alternates the horizontal scrollbar: ps. on macOS, this issue only happens if the "Show scroll bars" is set to "Always". Otherwise (where the scroll bars hide automatically) it's fine. |
fcddf83 to
2612447
Compare
|
@simurai Electron v1.4.2 disabled the native tabs support, so this shouldn't be an issue anymore 🎱 |
2612447 to
9df5253
Compare
f24e7e2 to
8bd2d16
Compare
|
electron 1.x is coming in atom 1.12? |
|
How long before this change will be merged into the master? |
|
I can't reproduce the find menu issue in safe mode, so it looks like that one was a false alarm. |
|
@kaiser101 We're facing some hard crashes with Electron when the dev tools are open. We may merge anyway and figure it out on master though. |
|
@steelbrain Unclear from your gif... Were you seeing lag scrolling the editor? If so, the lag could be due to longer pauses garbage collecting DOM nodes as we dropped the recycling strategy. @as-cii I wonder if we should revisit that. At some point we're gonna GC DOM and I worry those pauses could get long. It allocates quite a bit of memory. But first priority is these crashes I suppose. |
|
@nathansobo The editor was scrolling perfectly, the lag was only visible when scrolling search-and-replace tab (there would be white spaces in screen that would be filled later) |
|
@steelbrain That's definitely a find and replace bug and is worth reporting on that package if it hasn't been already. |
Adding a source map for the entire snapshot was expensive in terms of memory and seemed to be triggering some sort of bug in Chromium when reloading with the DevTools open. The custom row translation relies on a much more compact representation of the data and avoids the crash. Signed-off-by: Nathan Sobo <nathan@github.com>
Signed-off-by: Nathan Sobo <nathan@github.com>
|
Seems like AppVeyor failed but I believe that's just spurious. I will go ahead and merge it into master so that it can bake for a while before putting it on beta. Thanks everyone for the help and the hard work on this! 🙏 |






Reported Issues
os.tmpDir()deprecation warnings Upgrade Electron to v1.6.x #12696 (comment)tree-viewincorrect (Display the correct drag image on Electron >= 1.14 tree-view#1054)tabsandtree-viewmissing (Fix missing drop indicator on Electron >= 1.14 tree-view#1055, Fix missing drop indicator on Electron >= 1.4 tabs#426)dragovereventdataTransferobject (Fix mistakenly shown docks drop indicator on Electron >= 1.4 tabs#437)Reported issues resolved by #13880:
spec/text-editor-component-spec.jstestsDuring my initial testing on macOS 10.12, this seems to be working. Haven't noticed any regressions.
Would be great if more folks could give this a spin 🙇
/cc @atom/maintainers
Fixes #11692
Resolves #12690
Fixes #8006
Fixes #12832
Fixes #13767
Fixes #4084 (Will be fixed by the editor rendering rewrite)
Fixes #13265 (Will be fixed by the editor rendering rewrite)