Closed
Bug 1261457
Opened 8 years ago
Closed 8 years ago
Rich text editor fails because requests to about:blank are blocked
Categories
(Firefox for iOS :: General, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: aaronmt, Assigned: st3fan)
References
Details
(Keywords: losing-users, reproducible)
Attachments
(1 file)
Visit (you'll need to create or connect an account) http://forums.macrumors.com/forums/ios-9.183/create-thread Attempt to invoke focus to the thread body field. Nothing happens. This was reported from Maria. This is not reproducible in Safari (made a mistake yesterday when testing this). Noticed that in Safari/Desktop there's a formatting toolbar visible that's perhaps erring out in Firefox on iOS. Can this be web inspected remotely to check for errors?
Assignee | ||
Updated•8 years ago
|
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → bnicholson
Assignee | ||
Comment 1•8 years ago
|
||
I did a little bit of research: when I open the above URL in a minimal app that just has a WKWebView embedded without any of the infrastructure that Firefox adds, things work as expected. So we need to narrow down what in Firefox causes this. My guess is that this is most likely related to some UserScript that we inject.
Assignee | ||
Comment 2•8 years ago
|
||
The problem persists after disabling all user content scripts. Not sure what is going on here yet.
Assignee | ||
Comment 3•8 years ago
|
||
Also, not much useful in the web console.
Assignee | ||
Updated•8 years ago
|
Summary: Unable to invoke focus (keyboard invocation) to a an element with contenteditable in this case → Rich text editor fails because requests to about:blank are blocked
Assignee | ||
Updated•8 years ago
|
Assignee: bnicholson → sarentz
Whiteboard: [needsuplift]
Assignee | ||
Comment 4•8 years ago
|
||
This patch adds a special case for `about:blank` to the 'should we load this url' decision handler. It looks like `about:blank` is used to reset an iframe. We used to load these, but after https://github.com/mozilla/firefox-ios/pull/1576 (Bug 1251507 - Safari parity for url and scheme handling) we started to ignore them. That was a mistake :-/ This patch simply special cases `about:blank` and lets the `WKWebView` load them.
Assignee | ||
Updated•8 years ago
|
Attachment #8740236 -
Flags: review?(bnicholson)
Assignee | ||
Updated•8 years ago
|
Keywords: losing-users
Assignee | ||
Comment 5•8 years ago
|
||
I have marked this with losing-users because we know of at least two cases where people have said 'i cannot use this because i cannot use some website anymore'.
Comment 6•8 years ago
|
||
Comment on attachment 8740236 [details] [review] PR: https://github.com/mozilla/firefox-ios/pull/1703 LGTM!
Attachment #8740236 -
Flags: review?(bnicholson) → review+
Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [needsuplift]
Assignee | ||
Comment 8•8 years ago
|
||
Also, for reference, when you create a frame without a src, it defaults to about:blank. If we block that then page load events are never fired. Which breaks things that depend on this behaviour.
Reporter | ||
Comment 9•8 years ago
|
||
Are we taking this patch on 4.0?
You need to log in
before you can comment on or make changes to this bug.
Description
•