Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Fiefox Quantum v57.0 Buttons not working on some site

  • 11 การตอบกลับ
  • 9 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย CScotty

more options

On at least one site, and probably others, some "button" type features do not appear to work.

Specifically, I need to download the tracking script from Google AdWords. There is a button marked download but when I click it nothing happens. If I inspect the element it is this

Download tag

Not having the same problem if I use Chrome.

Any ideas?

On at least one site, and probably others, some "button" type features do not appear to work. Specifically, I need to download the tracking script from Google AdWords. There is a button marked download but when I click it nothing happens. If I inspect the element it is this <div class="content _ngcontent-mkx-19">Download tag</div> Not having the same problem if I use Chrome. Any ideas?

การตอบกลับทั้งหมด (11)

more options

Are you running an ad blocker of some kind? If so, then these would break activity on the actual ad websites themselves too. Either add the page as an exception so you can get what you need or temporarily disable the blocker, or use a browser that you don't have a blocker on to get the code.

more options

Thanks for the suggestion but, no I don't have any ad-blockers installed.

more options

Ok, can you test on a clean profile with nothing installed (meaning out of the box) and see if it still happens. I am wondering if perhaps something is interfering with it. Would be nice to eliminate that as the cause first.

more options

Could you rule out Firefox's Tracking Protection feature? When it is blocking content, a "shield" icon appears toward the left end of the address bar. More info in this article: What happened to Tracking Protection?.

more options

@GµårÐïåñ I'm not entirely sure I accomplished what you wanted. First, for grins, I tried 56.0 running under linux. Same problem.

Back to win 10, I renamed my profile to -old, uninstalled 57.0. Checked that no FireFox executables were left in the /Programs folder and re-installed. Sadly the installer managed to figure out my account and automatically synced and recreated the profile, so probably put things back to the same state, less any add-ons. Still have same problem.

@jscher2000 No tracking shield is shown.

เปลี่ยนแปลงโดย CScotty เมื่อ

more options

I have the same problem on many webistes. Most of Wix.com buttons for example don't work in Firefox. And when I talk about the issue the answer is : "contact Wix and ask them to be more compatible with Firefox"... Well guys Wix UI works in Opera, Edge, Chrome for all I know. And it worked in Firefox before the Quantum version. So maybe, just maybe it is nothing more than something Firefox needs to work on. I talk about Wix because it's obvious in there that Firefox 57.0 has html 5 compatibility issues. But it happened quiet a lot in other websites too. After two days of testing Firefox with the hope it was finally back to its glorious days, I moved back to Chrome. Again :(

เปลี่ยนแปลงโดย hansolocambo เมื่อ

more options

Hi hansolocambo, I did see your Wix thread and post a question for you there.

When you get a moment, could you mention other sites that have a problem that someone could view without needing to sign up for an account, if any?

more options

CScotty said

@GµårÐïåñ I'm not entirely sure I accomplished what you wanted. First, for grins, I tried 56.0 running under linux. Same problem. Back to win 10, I renamed my profile to -old, uninstalled 57.0. Checked that no FireFox executables were left in the /Programs folder and re-installed. Sadly the installer managed to figure out my account and automatically synced and recreated the profile, so probably put things back to the same state, less any add-ons. Still have same problem.

Well you went far beyond what I was asking, but thank you. For future reference, what I meant was creating a new profile in the sense that you launch Firefox with -p and click on create new profile and don't add anything to it and it will be out of the box for testing purposes. But what you did would accomplish that too, just more work on your end.

This might be how they are coding their CSS and how the new CSS engine is working to interpret them, that would be the most likely thing I can suspect at this point. Would you be willing to file a bug report and provide links and steps so that the devs can look into it?

more options

@GµårÐïåñ Ah! Thx! ...and ever so slightly embarrassed.

OK I've now tried that and I still have the same problem. Note that I had the same issue with 56.0. so this is not Quantum specific.

I'm thinking it might be time to file this as a bug.

more options

Not a problem, don't worry - now you know ;)

So it seems that it is indeed a CSS engine rendering issue and you are correct, I started experiencing this starting in 56 as well but mine as mostly clicking on links, the URL changes, but the document stays the same. But that was partially contributed by the way some frameworks were assigning the url, so ended up being caused by both in some instances, making it very difficult to know which belongs to which camp.

This would indeed appear to qualify as an actual bug for them to look into, can you please file the bug and for future reference of anyone who comes across this, post the bug link back here as well. Thank you.

more options

Just a small update. i continue to have the annoying bug.

I have not been able to file a bug report simply because every time it happens it's on a site that require a log on.


Maybe one of the developers could try?