Okay, I'll do what I can.
nsWindowGfx::Data32BitTo1Bit() crashes horribly with the usual error 0xC0000005 (EXCEPTION_ACCESS_VIOLATION_READ). It does so when called from nsWindowGfx::CreateIcon(), which itself is called from mozilla::widget::TaskbarTabPreview::SetIcon().
So chances are the taskbar preview icon data passed to CreateIcon() is pointing to ...
We have worked with our CDN provider to roll back a change that was made enforcing OCSP Must-Staple. Firefox should be back in business, sorry for the interruption. To keep up to date follow our StackStatus twitter account:
Well, since comments won't allow the ordinary strike formatting, someone there tried (and succeeded!) to trick the system by combining Unicode characters resembling English letters with a strike through them.
This results in one long stream of characters without any blank space, no different than:
Stack Exchange doesn't provide spell checking at all. It is your browser doing that, and it does work for question titles too on Chrome:
On Firefox though it can be an issue, although out of the control of the Stack Exchange developers. As one user commented:
As I know Firefox does spellchecking only for multiline edit boxes.
Which is the issue you ...
This is a really bad browser bug. And while we don't officially support FF 52, it seems used widely enough (because it's ESR) that this issue is probably worth working around.
Basically, the layout engine decides that the timestamp has a width of zero pixels, and we have to force the browser to re-calculate the layout.
This workaround is deployed here on ...
The image uploader already supports pasting an image, in browsers that support it.
Also see the original feature request (marked completed).
As a workaround until it's fixed, follow these steps:
Click "More login options"
Type https://openid.stackexchange.com into the "manually enter your OpenId" textbox
Click Submit and you will get the form, solid this time.
Pinpointed. The parent row is being set to display: block via an inline style, so it isn't being rendered as part of a table anymore and colspan gets completely ignored on the cell. Things just kinda break, badly, when you try to put a block directly inside a table like that. Removing that style seems to fix things.
Chrome seems to simply remove that style ...
tl;dr A normal spinner
I tried to find this out by looking on how this spinner is generated. Fortunately Stack Exchange documented their styles quite well on stackoverflow.design. They developed a framework called Stacks.
This button style is generated by the class is-loading. At first I looked whether it is an SVG but it uses an other trick.
This is a pretty common display bug that can be triggered in many ways: silly Unicode tricks, long code blocks, broken MathJax, missing MathJax delimiters, changing the font size in Chrome or in Firefox, etc. It was first reported a long time ago, and a server-side kluge was added to "fix" it (occasionally breaking code embedded in comments or very long ...
You can use a keyword search to add a custom search for Stack Overflow favorites:
Bookmark the URL
In the bookmark dialog, give this bookmark a keyword. sofavs for example.
Now you can search for favorites with:
sofavs search query
in your Awesome Bar. Firefox finds the bookmark by the keyword, ...
Off the top of my head, you'll want stackexchange.com, openid.stackexchange.com (assuming you use that), stackoverflow.com (and any other custom-domain sites of ours you may be logging into), stackauth.com, sstatic.net.
I think that should do it, but keep in mind that this list may change at any time and we don't intentionally support browser addons, so ...
We're doing some design overhaul on how comments are displayed; you can expect some weirdness while that's going on even though we're doing our best to test prior to pushing. No changes are going into how comments are displayed (or what gets displayed) as of yet, we're just changing how they're contained behind the scenes.
Some ephemeral breakage is to be ...
Solved from the comment left by e19293001 which pointed to this: Firefox asks for proxy details, but only when accessing facebook
Go to the URL about:config, search for the key network.websocket.enabled and switch it to false.
Now able to access SO without those annoying popups!
It appears that the cause of this bug is the same as for Pressing <Enter> in an input method editor should not submit comments, which affects IME users on various browsers, not just Firefox.
In both cases, the problem is that the event handler that the Stack Exchange UI uses to trigger comment form submission via the enter key is, for some peculiar ...
Now that Firefox has removed the preference that would allow a user to disable WebSockets, I decided to tackle this problem on my own and wrote WebSocket Disabler — a Firefox add-on that does exactly what its name suggests.
After installation, it adds a menu item to the Web Developer menu that can instantly enable or disable WebSockets:
I had the exact same issue with Firefox 22 on OS X 10.8.4 after an import of all my data (history + cookies + bookmarks etc.) from Chrome.
Removing all cookies from Firefox solved the problem.
In my case, I'm logging in SO with my Google account, so maybe removing only the SO / Google cookies would have worked. Did not use a very subtle approach here. Eh.
TBH that sounds exactly like adware or some kind of malware.
The first thing I would do is get malwarebytes and do a full scan. I also recommend you download Comodo Internet Security and do a scan with that aswell, and use that as your new AV system. The music is most likely comming from an ad running in the background.
Alot of online video sites have ...
Someone had already done the hard work of patching SlickGrid, so I forked the project and applied their changes (as the SlickGrid maintainer isn't able to work on the project right now), and then included the resulting file in Data Explorer.
Fixed now, pending a pull and redeploy. The result of pasting text copied across cells seems to be inconsistent ...
We all love Firefox's rendering engine quirks. Especially when they break jQuery's toggle().
Fixed by using toggleClass("dno"), but... seriously Firefox.
Fix is going out in rev 2015.12.23.4024 (meta) and rev 2015.12.23.3129 (main).
(kudos to bobince for the correct solution)
Like most web apps ...
The developer of uGet Integration addon is here.
This problem occurs if an addon loads content scripts into the addon.
I have fixed the problem and released new version 2.1.1 with the fix. Please upgrade your addon to 2.1.1
As noted in the comments to the post Comment timestamp is not showing in Firefox ESR, there are two workarounds for now for Firefox ESR 52.6.0.
Click on "show xx more comments" (if this is present).
Otherwise, open and close the Web Developer Inspector panel (Cntrl+Shift+C).
Hopefully, these will be needed only temporarily.
Update: It seems that the patch ...
It does not undo, it already does redo. Here is a simple test: Go to the answer box below, type something, and delete it. Then click the undo button, and you will see the redo button highlight. Instead of clicking it, click Ctrl+Shift+Z, and it should redo what you did.
I have done this in Chrome and in Firefox.