Created attachment 8719307 [details] script 1 - ellipsis in console 2016.02.14 16-34-52.html >>> My Info: Win7_64, Nightly 47, 32bit, ID 20160210071115 STR_1: 1. Open attached "script 1" 2. Open console (Ctrl+Shift+K) 3. Expand stacktrace 4. Click in the "Filter output" 5. Press Tab key 6. Move mouse over the area to the right from the scrollable box with stacktrace 7. Hold left mouse button, move mouse a bit to select some characters in script's name, wait several seconds, then release left mouse button (to avoid bug 1239992) AR: After you press left mouse button in Step 7, ellipsis become white, i.e. almost invisible ER: Ellipsis should stay visible
I couldn't reproduce this on osx, it may affect Windows only.
Priority: -- → P3
Summary: [e10s][APZ] Ellipsis in console become invisible if I focus console messages while a scrollable stacktrace is expanded → [APZ] Ellipsis in console become invisible if I focus console messages while a scrollable stacktrace is expanded
Firefox: 45.0, Build ID: 20160303134406 User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Hi, I have tested this issue on the latest Firefox (45.0) release and latest Nightly (48.0a1 - Build ID: 20160317030235) build and I have managed to reproduce it, but only on Nightly. If I disabled e10s, this issue is no longer reproducible. This suggests that it may be a e10s issue. This is a UI Firefox issue, and I don't believe it requires a test case. Arni could you please share your opinion on this? Thanks, Cosmin.
1) Well, I left "[APZ]" in the summary to indicate that this issue only happens with APZ enabled (layers.async-pan-zoom.enabled -> true). APZ was enabled in e10s in latest Nightlies. 2) The UI in console is (almost?) pure HTML, so it probably may be reproduced if I use the same HTML as testcase 3) I saw saw similar bug 1189438, bug 1185349, and I notised that APZ was causing OMTC bugs (layers.offmainthreadcomposition.enabled -> true) to happen in more cases than they usually happen. So there may be another underlying issue with a different regression range. I just didn't have enough time to complete the testing. Hopefully I will do it myself today.
You need to log in before you can comment on or make changes to this bug.