Created attachment 8359781 [details] onblur_alert_test.html User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release) Build ID: 20140113004002 Steps to reproduce: Run attached testcase in Aurora and Chrome. Actual results: Aurora fails. Chrome wins. Expected results: Both win.
The testcase works here; I think NoScript is causing problems again.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
Restarting with all addons disabled, the testcase shows an alert, but i can't click the OK button on it. Pressing Esc does dismiss it.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Summary: contentEditable span or div onblur doesn't get called → contentEditable span or div onblur alert can't be clicked
STR 1. Open attached testcase 2. Click two 3. Click one 4. Attempt to click OK button in alert box Regression window(m-i) Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/cbe04dbc2bd6 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131217160921 Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/08dc60299942 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131217161358 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=cbe04dbc2bd6&tochange=08dc60299942 Regresseed by: 08dc60299942 Blake Kaplan — Bug 933483 - Don't fire events (and especially request animation frame events) when we're in a modal dialog. r=smaug
Status: UNCONFIRMED → NEW
status-firefox27: --- → unaffected
status-firefox28: --- → affected
status-firefox29: --- → affected
tracking-firefox28: --- → ?
tracking-firefox29: --- → ?
Component: Untriaged → DMD
Ever confirmed: true
Product: Firefox → Core
I can also reproduce the problem on Linux.
OS: Windows 7 → All
Blake, can you please take a look? Thanks!
Assignee: nobody → mrbkap
Tracking for website breakage risk.
tracking-firefox28: ? → +
tracking-firefox29: ? → +
Created attachment 8366306 [details] [diff] [review] clear capturing content
Comment on attachment 8366306 [details] [diff] [review] clear capturing content SetCapturingContent is static, so you don't need to get the presshell.
Attachment #8366306 - Flags: feedback?(enndeakin) → feedback+
Ah, yes. Shouldn't have copied that part from above.
Created attachment 8366713 [details] [diff] [review] clear_capturing_content_when_entering_modal_state_2.diff
https://hg.mozilla.org/integration/mozilla-inbound/rev/042a31391d55 mrbkap, on which branches do we need this?
The bug that caused this is koi+. Could we get this to all relevant trees?
Flags: needinfo?(mrbkap) → needinfo?(sheriffs)
That's not at all a decision for sheriffs to make.
blocking-b2g: --- → koi?
Flags: needinfo?(sheriffs) → needinfo?(release-mgmt)
status-b2g18: --- → unaffected
status-b2g-v1.1hd: --- → unaffected
status-b2g-v1.2: --- → affected
status-b2g-v1.3: --- → affected
status-b2g-v1.4: --- → affected
Comment on attachment 8366306 [details] [diff] [review] clear capturing content Obsoleting in favor of the patch that was checked in. Olli, I believe that this will need to apply on Aurora and b2g26_v1_2.
Attachment #8366306 - Attachment is obsolete: true
We're no longer maintaining 1.2, so moving to 1.3 for triage.
blocking-b2g: koi? → 1.3?
Status: NEW → RESOLVED
Last Resolved: 4 years ago → 4 years ago
status-firefox29: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
1.3+ for compatibility of website issue
https://hg.mozilla.org/releases/mozilla-aurora/rev/95af3eb13175 My understanding was that we're still taking some patches for v1.2 if they affect partner qualification? I guess we don't expect this bug to significantly affect that?
status-b2g-v1.3: affected → fixed
status-b2g-v1.4: affected → fixed
status-firefox28: affected → fixed
(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #18) > https://hg.mozilla.org/releases/mozilla-aurora/rev/95af3eb13175 > > My understanding was that we're still taking some patches for v1.2 if they > affect partner qualification? I guess we don't expect this bug to > significantly affect that? To my understanding, we don't have any partners lined up using our 1.2 branch right now.
From a relman perspective we will not be picking up the issue in 1.2.
You need to log in before you can comment on or make changes to this bug.