KilliK wrote:thanks, the tooltip info is better. but what about the greyed out non-e10s window command?
It's not greyed out for me either. Perhaps an add-on is causing it or some css code your are using? Try running in safe mode and/or with a new profile to see what you get.
What non-e10s Windows command, it was removed AFAIK. I don't see it anywhere in the 'menu' or the 'hamburger' panel.
KilliK wrote:thanks, the tooltip info is better. but what about the greyed out non-e10s window command?
It's not greyed out for me either. Perhaps an add-on is causing it or some css code your are using? Try running in safe mode and/or with a new profile to see what you get.
What non-e10s Windows command, it was removed AFAIK. I don't see it anywhere in the 'menu' or the 'hamburger' panel.
Ran with a new profile and non-e10s commands were present.
Intel i9-13900K | ASUS ROG MAXIMUS Z790 HERO DDR5 | 64GB CORSAIR VENGEANCE DDR5 @ 6600 Mhz.
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
1157467 - test_request_context.html leaks when run with e10s 1129564 - [e10s] anchor navigation from the awesomebar removes the lock icon 1134518 - Incorrect back-forward navigation in tab with lots of history and e10s enabled 1155789 - [e10s] Null deref in nsFrameLoader::DoSendAsyncMessage 1151597 - Stream e10s memory reports over IPC instead of sending one big array. 1056146 - Fix zoom tests in browser/base/content/test/general/ (using FullZoomHelper) to work in e10s 1134769 - [e10s] BrowserUtils.jsm spams the web console with "unsafe CPOW usage" warnings because of getFocusSync 982319 - [e10s] Network monitor and webconsole need to decode gzipped response bodies in the client 1158805 - [e10s] Re-enable browser_bug970746.js 1074233 - [e10s] Make the GCLI screenshot command work in e10s. 1127756 - [e10s] The gcli highlight command does not work anymore 1157512 - [e10s] Decrease the plugin hang timeout from 45 seconds to ??? for e10s plugins 1156515 - Remove "New e10s window" option 1100502 - about:webrtc Start Debug Log/etc don't work on Nightly (e10s) 1154877 - Content process shouldn't use the Places Database 1156613 - Fix e10s blocks conditioned to NIGHTLY_BUILD (and others) in preparation for Aurora merge 1083365 - [e10s] Tooltips don't always go away 1095475 - [e10s] Remove Underline from tabs 1159327 - [e10s] Accessibility blacklist client work 1156057 - Right-clicking an image throws an error 1156592 - Add Telemetry probe to measure async tab performance 1152585 - [e10s] child offset is calculated incorrectly when browser.tabs.drawInTitlebar=false on OS X 1156591 - Add Profile markers for async tab switch performance profiling 1129040 - [e10s] Plugin block list tries to load blocklist and triggers exception in FileUtils.jsm 1096834 - e10s disabled due to accessibility when connecting with Microsoft Remote Desktop 1108607 - Touch input devices have e10s disabled due to accessibility 1158810 - [e10s] Re-enable browser_424101.js 1160217 - Intermittent browser_responsiveuiaddcustompreset.js | add preset, and selected in the list, dimension valid (width) - Got 1151, expected 456 | add preset, and selected in the list, dimension valid (height) - Got 783, expected 123 1081879 - [e10s] Can not get nsIHttpChannel in nsIWebProgressListener.onStateChange
Ran with a new profile and non-e10s commands were present.
ok, found the culprit, it was the single window mode setting in TMP. now it works and I like how you can instantly use the e10s incompatible addons in the new non-e10s window. ofc , the ideal will be everything to work flawlessly in e10s mode.
KilliK wrote:why did they do it? can we bring them back? I want some kind of indication to know which profile is running or not e10s.
also, I noticed the command in the menu bar to open a non-e10s window, is now greyed out. why?
They did it because the release won't have underlines, and I don't know how you would get them back.
Not greyed out in the Linux version.
Linux build is older
Micro gaming box: AMD A10-7800 APU, 8gb RAM M350 ITX case (size of a book), Windows 10/Ubuntu Tablet/Laptop: Asus Transformer T100, Intel Atom 2GB RAM, Windows 10 x86 Mobile:Xiaomi Redmi Note 3 Pro
well, they have 5 versions until the official release, to improve it. so far they have fixed the compatibility for many addons, they reduced the crashes, but the responsiveness issue still remains and it is even worse than the non-e10s version of the browser. I hope this will change by the end of 2015.
Ezh wrote:With this throbber FF cannot be shipped for normal user...
Which is what he says in the blog post....
Micro gaming box: AMD A10-7800 APU, 8gb RAM M350 ITX case (size of a book), Windows 10/Ubuntu Tablet/Laptop: Asus Transformer T100, Intel Atom 2GB RAM, Windows 10 x86 Mobile:Xiaomi Redmi Note 3 Pro
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.