Hot answers tagged

15

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 ...


14

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: https://twitter.com/StackStatus/status/1133791399189463040


12

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: sincecommentswon'tallowtheordinary<strike>strike<...


11

For me, clearing the cache did not solve the issue, but clearing the stack exchange cookies did. Look here for instructions on how to clear cookies from individual websites. (When I did this, I cleared the cookies for stackexchange, stackoverflow, and superuser.)


10

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 ...


9

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 ...


8

When you search for a word that is also a top 40 tag, in this case 'c++' and 'windows', it does a tag search instead. See this blog post for details. Since you're hiding ignored tags, you're hiding all the search results. If don't want it to convert your search terms to tags, put it in quotes. It will still be hidden if the question is tagged 'windows' ...


8

The image uploader already supports pasting an image, in browsers that support it. Just copy the image, open the image upload dialog box in the Stack Exchange editor, and paste. It's all done in JavaScript withthe DataTransfer interface. Also see the original feature request (marked completed).


7

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.


6

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 ...


5

This will be fixed in the next build (after rev 2012.5.30.2722).


5

I had the same problem on Firefox, what worked for me was adding an exception on my proxy settings for sockets.ny.stackexchange.com that way it just fails silently for that address instead of asking for authentication.


5

Firefox for Android is not a browser we support (first of all, it's still in beta), but since the fix is easy enough and it is indeed unlikely that FF will change this, I've cleared the float for the next build. Just for the record, that Firefox Help answer says: This problem has appeared in sites for years, and it seems unlikely that Firefox will change ...


5

This is not an error. Questions with your favorite tags will have a yellow background. I think there's even some automatic detection of your most active tags and those get auto-favorited (don't quote me on that).


5

This is an old Firefox version 3 bug. Not just on this site. Haven't seen it yet in 4 and 5 so it probably got fixed.


5

You're exhibiting this error. The first person I've actually got "on the line" who has encountered it. I'm going to go out on a limb and say this is your ISP doing something very... internet-breaky. IE 9 working (I'm guessing intermittently) is odd, but I can imagine bogus caching rules that would allow it. Anyway, from your IP address I've logged the ...


5

You're reading too much into that FAQ. That page is maintained and updated by the community, and is not intended to be an exhaustive list of browsers and versions that are or are not supported. We're committed to supporting the current version and one previous major version of major browsers. We're not gonna actively break the sites on older versions or ...


5

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 ...


5

Already fixed and in the next build. This was also affecting drag-n-drop on Opera.


5

You can use a keyword search to add a custom search for Stack Overflow favorites: Bookmark the URL https://stackoverflow.com/search?q=infavorites%3Amine+%s 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, ...


5

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 ...


5

Thanks for reporting. I have pushed a fix internally, and now waiting for the next build for the fix to be published across the network. Should be status-completed in couple hours.


5

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 ...


5

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. They ...


4

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 ...


4

According to the OP, this problem was caused by an unspecified Firefox add-on, and is resolved. Please upvote this answer to get this question off the "unanswered" list.


4

It seems unlikely since Stack Exchange already doesn't show data live -- your inbox doesn't light up as soon as you get a notification, you need to load a new page. It's more likely this could be folded into a user script like SO Live! that already does live page updating. I don't know if a script like that exists for inbox notifications (SO Live! only does ...


4

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:


Only top voted, non community-wiki answers of a minimum length are eligible