Every now an then, I experiences input boxes stop accepting text. If I restart the browser everything is fine. It's hard to replicate. Google docs and gmail are where I experience this the most. I am using nightly 64 bit with e10s turned on.
I think those sites use <div contenteditable> rather than form controls (<input> or <textarea>). Can you check? (using devtools)
Looks like <div contenteditable> <div tabindex="1" style="direction: ltr; min-height: 85px;" role="textbox" g_editable="true" id=":3mg" class="Am Al editable LW-avf" hidefocus="true" aria-label="Message Body" contenteditable="true"><br></div>
Thanks, this is probably an Editor / e10s issue then. Perhaps it would help narrow it down if you run with e10s turned off for a while and see if the problem disappears?
Component: Layout: Form Controls → Editor
Given that these are top100 sites, this should probably block shipping e10s.
Severity: normal → major
tracking-e10s: --- → ?
I'll try to find reliable STR's and whether it's worse on e10s or not.
Sorry about that Martin. I meant to NI myself.
Flags: needinfo?(mbest) → needinfo?(twalker)
NP. Again, wish I had better duplication steps. As far as I can tell so far it happens randomly and fairly infrequently. Have not been able to find a repro case yet. I have seen it happen with and without e10s turned on.
Whiteboard: btpp-active btpp-follow-up-2016-03-03 → btpp-follow-up-2016-03-10
per comment 7, not e10s specific.
tracking-e10s: ? → -
2 years ago
Whiteboard: btpp-follow-up-2016-03-10 → btpp-follow-up-2016-03-10 [platform-rel-Google] [platform-rel-Gmail]
2 years ago
Whiteboard: btpp-follow-up-2016-03-10 [platform-rel-Google] [platform-rel-Gmail] → btpp-follow-up-2016-03-10 [platform-rel-Google] [platform-rel-Gmail][platform-rel-GoogleDocs]
Are you still experiencing this, Martin?
I have not run into this lately. I have been using nightly pretty aggressively and have not run into this in some time. Martin
I don't see anything to do here without more specific steps to reproduce, especially given comment 10.
Let's re-open this if it starts happening again.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.