See bug 881087.
Mats has a patch in progress in bug 881832, so I'm going to assign this to him. Also, it sounds like this is therefore a layout bug and not DOM?
Assignee: nobody → matspal
status-b2g18: --- → affected
status-firefox26: --- → affected
status-firefox27: --- → affected
status-firefox28: --- → affected
status-firefox-esr17: --- → wontfix
status-firefox-esr24: --- → affected
tracking-firefox27: --- → +
tracking-firefox28: --- → +
status-firefox26: affected → wontfix
status-firefox29: --- → affected
tracking-firefox29: --- → +
Hey :mats, any updates here on next steps given we are a couple of beta's away from shipping firefox 27 ?
I still need to figure out the last test failure in bug 881832, which has proven rather elusive so far. Besides, the patch in bug 881832 has a high risk for regressions so I wouldn't recommend it for beta.
(In reply to Mats Palmgren (:mats) from comment #3) We're a couple of betas into FF28 now - if comment 3 is still the case, we can no longer track for 28 anymore. Please update with current status.
No change since comment 3.
Assignee: matspal → nobody
Clearly tracking this isn't useful.
tracking-firefox28: + → -
tracking-firefox29: + → -
tracking-firefox28: - → ---
tracking-firefox29: - → ---
Jet, is there somebody who can get bug 881832 over the finish line? This sec-high bug is almost a year old now.
Working on it...
Johnny, can you please find somebody to work on this? The actual work is happening in bug 881832, which has had a reviewed patch since June 2013, but it causes test_hover.html to fail. Every few months somebody unbitrots the patch and confirms that the test still fails but nobody has actually fixed it yet, and that has been going on for two years now. Thanks.
Flags: needinfo?(bugs) → needinfo?(jst)
In bug 881832 there is some pretty recent work and we seem close to a fix. Since this is sec-high, I'd like to track it for 47 in hopes we can make progress.
status-firefox47: --- → affected
tracking-firefox47: --- → +
mats, any luck here? I would love to get this fixed in 47.
Sec-high issue that is tracked for 47, changing the flag to blocking so it gets some attention.
tracking-firefox47: + → blocking
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #11) > mats, any luck here? I would love to get this fixed in 47. Not really, I've tried a few times to sort out the issues in bug 881832, but it doesn't seem to work, so I have given up on that one, sorry.
Matt has some patches up for review in the public bug, so I'll assign this to him. Hooray!
Assignee: nobody → matt.woodrow
Removing the blocking flag as we have had this issue for a few releases now.
status-firefox47: affected → wontfix
tracking-firefox47: blocking → +
status-b2g18: affected → ---
status-firefox26: wontfix → ---
status-firefox27: wontfix → ---
status-firefox28: affected → ---
status-firefox29: affected → ---
status-firefox30: affected → ---
status-firefox48: --- → affected
status-firefox49: --- → unaffected
status-firefox-esr17: wontfix → ---
status-firefox-esr24: affected → ---
tracking-firefox27: + → ---
I don't actually have access to the bug in comment 0, but I believe my patches in bug 881832 are sufficient to fix this.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox49: affected → fixed
Resolution: --- → FIXED
status-firefox50: --- → fixed
status-firefox-esr45: --- → affected
[Tracking Requested - why for this release]: We should have landed this one on ESR-45 to go with the 49.0 release. Too late?
status-firefox48: affected → wontfix
tracking-firefox-esr45: --- → ?
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-main49+]
Summary: <iframe src> fragment timing attack can steal private data → <iframe src> fragment timing attack can reveal private data
We had several chances to get this in 49. The patches in bug 881832 are kind of large and look to be related to bugs in Google Docs, sheets, etc. I haven't sorted out whether those bugs were regressions caused by it and now fixed, or whether they were made dependencies later to make it clear what fixed them. But I'm reluctant to uplift this to ESR until we see what kind of regressions pop up once it hits the release channel. This looks to me like the sort of change where we may not get the same broad user coverage on beta as we will on release.
Please feel free to argue otherwise - I'll leave this as tracking-esr45:? for the moment.
When this lands on ESR we should also uplift the fix for bug 1293985 and likely other from the depends-on bugs mentioned here. Matt, does that make sense to you?
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #20) > When this lands on ESR we should also uplift the fix for bug 1293985 and > likely other from the depends-on bugs mentioned here. Matt, does that make > sense to you? Yes, definitely.
Andrei, making sure you have access to this bug for testing ESR.
Looks like this landed 6 days ago on esr45, in bug 881832.
status-firefox-esr45: affected → fixed
You need to log in before you can comment on or make changes to this bug.