Closed
Bug 1487887
Opened 6 years ago
Closed 6 years ago
Cannot click "x" (close) button on specific websites
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 218415
People
(Reporter: e412byoy7, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180807170231 Steps to reproduce: Click "x" on bottom right of this website: https://www.rocketleagueesports.com/news/introducing-fan-rewards--phase-3-/# Actual results: nothing Expected results: should've closed window on bottom.
Comment 1•6 years ago
|
||
Do you mean the "x" button of a tab or the "x" button of a whole window or something different ? I do not have any issues closing a window or a single tab with that page loaded.
Component: General → Untriaged
Flags: needinfo?(danielboontje)
x of the privacy policy notification window on bottom of screen.
Flags: needinfo?(danielboontje) → needinfo?(bugzilla)
Comment 3•6 years ago
|
||
right, I missed the "bottom" in your coment#0. I can see the issue now with Firefox 61 but it works in a current Firefox nightly build. The checkin from bug 218415 fixed this according to mozregression. I will mark this as dupe of bug 218415, this should be fixed in Firefox63.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(bugzilla)
Resolution: --- → DUPLICATE
Is this fixed also already in Beta FF build?
Flags: needinfo?(bugzilla)
Comment 5•6 years ago
|
||
The Firefox stable release version is currently 61, the beta build is curently at version 62 and the nightly builds are at version 63. According to https://wiki.mozilla.org/Release_Management/Calendar the fixed versions will become a beta very soon (2018-09-04) and the fix will appear in a normal Firefox release around 2018-10-23
Flags: needinfo?(bugzilla)
Updated•6 years ago
|
Component: Untriaged → DOM: Events
Product: Firefox → Core
Can confirm is fixed in Beta 63.0. To FF 63 release it is suuper long, can we please make this the "event"-problem a hotfix for for example FF release 61.0.3 ? (as it is a website that has an impressive traffic over 4 million views per month of which probably 1-2 million alone are already from Firefox 61.0.2). Would be very much appreciated. (source for the visits-statistics website: https://www.similarweb.com/website/rocketleague.com#overview )
Flags: needinfo?(gingerbread_man)
Flags: needinfo?(bugzilla)
Please read the above comment and also the first post, it is about the "event" problem where Firefox still doesn't identify an "event" as event when not declared previously (compared to Chrome browser, which does identify the "event" function even then.)
Flags: needinfo?(miket)
Comment 9•6 years ago
|
||
bug 218415 is an enhancement for Firefox and not a real bug. Such a high risk code change will never go into a point release like 61.0.3 and it's unlikely that this will go into Fx62 because it the branch date to beta is soon but you can ask in bug 218415 if they uplift it to Fx62. It would be much easier to add a workaround on the page itself.
Flags: needinfo?(bugzilla)
Comment 10•6 years ago
|
||
I don't have anything to do with uplifts. Bug 218415 was filed on 2003-09-05, nearly 15 years ago to date. It has amassed 80 comments and about 33 related bug report links. The whiteboard lists it as a top priority web compatibility issue. It hasn't flown under the radar. A beta uplift would've likely happened by now, if it'd been deemed wise. I don't think that's going to happen now, with less than 1 day to go.
Flags: needinfo?(gingerbread_man)
Reporter | ||
Comment 11•6 years ago
|
||
ok posted in bug 219415. Also, I accidently had posted the wrong link initially.
Flags: needinfo?(miket)
Comment 12•6 years ago
|
||
Thanks for your patience -- I agree it feels like a long time to wait, but the longer we let this kind of change "bake" in pre-release versions, the more likelihood it will stick around permanently. :)
Reporter | ||
Comment 13•6 years ago
|
||
I just want to express my concern that the longer it takes (most FF users only use release version), the more likely that those of the 500.000 rocketleagueesports.com visitors who are on FF start to use Chrome...
Flags: needinfo?(miket)
You need to log in
before you can comment on or make changes to this bug.
Description
•