200

We have updated the jQuery version that Stack Overflow and Stack Exchange use from version 1.7.1 to 1.12.4 today (Tuesday, September 27, 2016). jQuery is an infrastructure library, and we've been running on an old version for a while because it worked well. However, there are a few improvements and features that made it compelling for us to upgrade, especially since some parts of the site already used a different version.

As a user of our Q&A sites, nothing should visibly change, as this is an infrastructure rather than a feature update. However, with an infrastructure update like this, there is always a chance for things to slip through the cracks.

If you encounter functionality that used to work yesterday and is broken today, please leave an answer on this thread and accept my apologies in advance.

Please be aware of our browser support matrix.

Do note that userscripts that rely on deprecated jQuery functionality (like .live() - anything in the 1.7, 1.8, 1.9 and 1.10 category, and if you can in the 3.0 as well to make a future update less likely to break your script) may need to be updated. There were no DOM or other structural changes, so selectors should still be the same.

If you're curious why we're going to jQuery 1.12.4 and not 3.1, this is a matter of incrementally upgrading and making sure things work along the way. Pretty much every 1.x version had major changes, and jQuery recommends upgrading an old 1.x version to the latest 1.12.4 and jquery-migrate 1.x plugin first and fix anything that is deprecated. We are in this stage now and want to make sure everything still works.

  • 30
    Should bug reports related to this change be reported here as answers, or as new questions? (i.e. what will have better chance to be noticed?) – Shadow Sep 26 '16 at 17:49
  • 235
    -1 not enough jQuery – user3459110 Sep 26 '16 at 17:50
  • 3
    @ShadowWizard Once the update is live, I'll add a call to action to this post here to ask people to submit bugs as answers, although I'll be watching the new questions feed on Meta.SE and Meta.SO in any case. – Michael Stum Sep 26 '16 at 17:50
  • 22
    So you're just going to use jQuery? – Machavity Sep 26 '16 at 17:53
  • 3
    @ShadowWizard Mostly perf and browser compatibility, and some plugins that require a newer version. Better CSS3 support, better source map support, better typescript integration - no one "must have" feature, but 4 years of incremental bugfixes and improvements. – Michael Stum Sep 26 '16 at 17:59
  • 5
    Awesome, thanks and good luck with fixing the bugs that ought to follow. :) – Shadow Sep 26 '16 at 18:05
  • 4
    If the developers of SE write minified vanilla JS backwards, why would they need jQuery..? – user340896 Sep 26 '16 at 18:28
  • 4
    Thanks for the heads-up (and for the update)! Looks like SOUP should be fine (fingers crossed!), although I'll need to remove a couple of .andSelf()s in the next update. – Ilmari Karonen Sep 26 '16 at 18:45
  • 30
    @AwalGarg But it'll be newer jQuery now, so that we can add more with less effort :) We might even get basic arithmetic. – Michael Stum Sep 26 '16 at 19:16
  • 24
    Just use $.installJquery() and you're done! – Chris Sep 26 '16 at 20:12
  • 2
    One step at a time. – Shyju Sep 26 '16 at 22:15
  • 5
    You mean no more "Use of getAttributeNode() is deprecated. Use getAttribute() instead." and "Use of getPreventDefault() is deprecated. Use defaultPrevented instead." console warnings? jQuery just isn't the same without them. :( – Alexander O'Mara Sep 27 '16 at 4:15
  • 4
    @ShadowWizard And we're live! – Michael Stum Sep 27 '16 at 16:02
  • 3
    @TylerH Minimizing Headache. The big breaking version is jQuery 1.9 which removed all the old stuff. 2.x would also have worked, but then it would be a bigger question of "is stuff broken because of the deprecated functionality or because a browser is no longer supported?". Once the code is working on 1.9+, moving to 3.x should be relatively easy. We're on Step 5 of the 3.0 upgrade guide, so we'll skip over any 2.x headaches. – Michael Stum Sep 27 '16 at 19:38
  • 8
    Developing for SE must be nice with so many tech savvy users to help you track down bugs :D – Blackhawk Sep 27 '16 at 20:40

17 Answers 17

40

This is now


When you are on any page on any Stack Exchange site, when you focus on search bar, and then defocus(clicking below the search bar), it makes unintended animation of search bar and also along with badges and profile picture div:

(Once, if you focus and unfocus again it doesn't happen.)

This is happening in all sites of Stack Exchange.

If you type something in search bar, then it doesn't happen.

If you need to reproduce it, you need to reload the page to see it in effect.

  • 7
    Also if you write something, then delete what you wrote and unfocus, the placeholder text is not displayed as it should. – Shadow Sep 28 '16 at 7:26
  • 2
    Both are resolved now. That was some truly old functionality, incl. IE8 workarounds. – Michael Stum Sep 28 '16 at 18:11
  • 1
    @Michael thanks, I'm pretty sure I noticed the placeholder issue before, but never bothered to report. The jumping textbox is the winner bug so far though... ;) – Shadow Sep 28 '16 at 19:24
26

This is now


Enter key no longer submit a comment when pressed, as it used to do before.

Observed both when adding a comment and when editing a comment.

It does work on per-site metas, i.e. bug applies to all main sites. (including MSE)

Browser: Chrome latest stable (53), Windows 10.

  • Pushed a fix for this, should now work again on all sites and metas – Michael Stum Sep 27 '16 at 17:15
  • Indeed, it does work again! What tab completion? In comments? It does work here. – Shadow Sep 27 '16 at 17:15
  • Yes, I forgot our own rules about tab completion (1. Only list people in the comment thread, 2. Don't list yourself or the owner of the Q/A that's being commented on) – Michael Stum Sep 27 '16 at 17:18
  • 3
    @Michael thanks, any juicy details why Enter didn't work? :) – Shadow Sep 27 '16 at 17:28
  • 2
    The rules for the :visible selector have changed, or rather the order in which things are checked. Trying to figure out the exact differences and where else it might happen, but compare jQuery.expr.filters.hidden between jQuery 1.7.1 and jQuery 1.12.4 – Michael Stum Sep 27 '16 at 17:34
  • 3
    @Michael thanks for the details! And on a side note, thanks for fixing this other bug, though probably only as a side effect! :-) – Shadow Sep 27 '16 at 17:37
20

This is now


When adding a picture to a post, if I paste a URL, the "Add Picture" button never activates. Instead, I need to upload a copy of the picture (or manually enter Markdown to point at the external URL)

In active add picture link

  • 15
    Fix pushed, should work again now. (technical info: seems that input[value!=""] is no longer a valid selector) – Michael Stum Sep 27 '16 at 18:02
  • @MichaelStum huh, got to love all those small yet breaking changes, that probably are not documented anywhere... ;) – Shadow Sep 28 '16 at 7:22
  • @MichaelStum ShadowWizard The API site says its still valid... – curiousdannii Sep 29 '16 at 1:26
  • 1
    It is indeed still valid – David Hedlund Sep 29 '16 at 13:46
  • I have issues with uploading images on tex.stackexchange using Chrome in Windows 10. When clicking on "Drag and drop or click here" there is a lag of several seconds between the click and the Windows Explorer window opening. The Add Picture box is also greyed out and unusable. – ahorn Sep 29 '16 at 14:13
17

This is now


It appears that moderators can no longer decline flags with a custom reason. When we go to decline a flag and choose the "other" option, no text box appears and we can't enter a reason:

enter image description here

I observed this on Safari 10.0 running on macOS Sierra (10.12), and another moderator reproduced it in Chrome. They stated that forcibly running

$("#dis_Other").toggle()

will bring back the text box.

  • 6
    workaround: stop declining flags. :) On a more serious note, does the similar feature to reply to helpful flags work? – gnat Sep 28 '16 at 15:53
  • 1
    @gnat - The text box does show up for custom helpful flag acceptances, just not for the custom flag declines. We can only decline with the canned reasons at present. – Brad Larson Sep 28 '16 at 15:55
  • 3
    This is resolved now. – Michael Stum Sep 28 '16 at 16:38
  • @MichaelStum - Thanks for the quick turnaround. Appreciate the help. – Brad Larson Sep 28 '16 at 17:06
  • Can we change this to status-intended? Stupid custom flags... for every good custom flag there's 10 that could have used a non-custom like word for word, I swear... – corsiKa Sep 30 '16 at 17:26
12

This is now


Searching for a badge to track progress on results in dozens of the same badge

As reported on Meta Stack Overflow by Sean Vieira:

Steps to replicate

  1. Navigate to your profile
  2. Click on the "Choose which tag badge to track" gear icon
  3. Search for a tag name

Expected results

  • The tag badges for the matching tag will be displayed (bronze, silver, and gold).
  • Only the tag badges matching the query will be shown (so for a perfect match, only three tag badges will be shown

Actual result

  • The bronze badge is show dozens of times (see screenshot)
  • No silver or gold version of the badge is shown at all.

Searching for typescript in the "Select your next badge" popup, showing dozens of bronze typescript badges

This seems to be related to the changes in the .replaceWith(), .after() and .before() methods. From jQuery documentation:

Prior to jQuery 1.9, .replaceWith() would attempt to add or change nodes in the current jQuery set if the first node in the set was not connected to a document, and in those cases return a new jQuery set rather than the original set. The method might or might not have returned a new result depending on the number or connectedness of its arguments! As of jQuery 1.9, .after(), .before(), and .replaceWith() always return the original unmodified set. Attempting to use these methods on a node without a parent has no effect—that is, neither the set nor the nodes it contains are changed.

The bug is probably in the replaceAvailableInDom function in the the user.en.js file.

  • This should be fixed now. Interestingly, it didn't happen in Meta. – Michael Stum Sep 28 '16 at 18:08
11

When I hover over "delete" link (link to example post) popup doesn't tell me that I already voted.

Windows 10 / Firefox 49.0, Chrome 53.0.2785.116 m, Edge 38.14393.0.0.

example screen shot with missing you-voted part


Prior to change it did, see for example Mouseover tooltip for delete count is wrong

example old screen shot with present you-voted part

  • Not sure that this is related to the jQuery change. I have occasionally seen it not tell me that I'd voted to delete when I had. It didn't happen often enough for me to detect a pattern, however. – ale Sep 28 '16 at 13:23
  • 1
    @AʟE. same here - prior to recent change it sometimes / infrequently missed but mostly was there. After the change it is 100% missing always – gnat Sep 28 '16 at 14:02
  • 1
    I think it happens right after you cast the vote, but after you reload it's fine. Can you please check it? (If that's the case, it's still a bug, but not related to the jQuery upgrade.) – Shadow Sep 28 '16 at 19:27
  • reload doesn't help @ShadowWizard – gnat Sep 29 '16 at 4:44
  • It didn't show for me weeks after casting my del vote. However, I'm almost entirely certain that the behaviour predates the jquery change (last time I looked for things to delete vote was weeks ago, yet I remember this bug from then). – Andras Deak Oct 1 '16 at 23:24
  • 1
    @AndrasDeak I use this feature every day and to me it broke only recently. It was somewhat unstable before though – gnat Oct 2 '16 at 0:22
  • similar complaint at MSO: Why a vote to delete button doesn't show I already voted? – gnat Oct 6 '16 at 14:30
10

Not sure if this is related, but it looks like fonts on error popups are missing and the browser falls back to the default font.

enter image description here

enter image description here

  • Checking. What browser are you using? – Michael Stum Sep 27 '16 at 18:31
  • @MichaelStum Firefox. The first screenshot was also reproduced in Edge. – André Borie Sep 27 '16 at 18:33
  • 1
    This is unrelated but a bug. .message-text has no font because it's usually set by a parent container, and in these cases there isn't one. (For reference, font should be Arial,"Helvetica Neue",Helvetica,sans-serif but no CSS rule matches here) – Michael Stum Sep 27 '16 at 18:43
  • I winder if this is in some way related to tags losing some of their formatting randomly (seen on SO and MSO) – Machavity Sep 27 '16 at 18:48
  • @MichaelStum should I report this in a separate question then? – André Borie Sep 27 '16 at 19:03
  • @AndréBorie If you wouldn't mind, that would be awesome. – Michael Stum Sep 27 '16 at 19:36
  • @Machavity Might that have been this issue? meta.stackexchange.com/questions/285046 – Michael Stum Sep 27 '16 at 19:53
  • @MichaelStum Yep, that's it – Machavity Sep 27 '16 at 20:19
  • 3
    I'm curious. What do you have to do to get a "These profiles are the same" error popup? – Rand al'Thor Sep 27 '16 at 23:01
  • 2
    @randal'thor on the contact form, ask to merge accounts. This will bring up two fields for the old and new profile, and validation actually checks whether they're the same. – André Borie Sep 27 '16 at 23:04
  • @AndréBorie did you just stumble upon that or do you actually normally test such obscure things? – user3459110 Sep 30 '16 at 7:41
  • @AwalGarg for the first one I hovered my mouse over the dupehammer badge accidently. The second one I had to use the contact form. I usually don't bother testing anything unless I'm paid to do it. – André Borie Sep 30 '16 at 13:34
10

It appears as though the reputation graph is no longer accepting drag events, making it impossible to move about the graph:

enter image description here

  • 1
    What Site and Browser? it works fine on mine in Chrome 53.0.2785.116 on both Meta.SE and Stack Overflow and i've purged my cache from the beginning of time – Memor-X Sep 29 '16 at 5:42
  • I'm seeing it on Chrome 53.0.2785.116 as well on AskUbuntu. Let me try purging caches again (result: no difference). – Kaz Wolfe Sep 29 '16 at 5:43
  • 1
    I can't even drag the selection (i.e no visible selection at all). Chrome 53.0.2785.116 OS X, works fine on all other browsers. – Cai Sep 29 '16 at 8:57
  • Works fine also here: Chrome Version 53.0.2785.116 (64-bit), FF 47.0, IE11 – toesslab Sep 29 '16 at 9:42
  • Cannot repro either on any browser on Meta, SO and AskUbuntu, but I'll take a look at the code later to see if there's anything that looks problematic. – Michael Stum Sep 29 '16 at 15:54
  • Works fine for me on AskUbuntu using Chrome Version 53.0.2785.116 m (64 Bit, Windows). – MrWhite Sep 29 '16 at 15:54
  • 1
    Pretty sure this is not related to the new jQuery. This feature has worked intermittently (at best) for several months, at least for me. I actually think it never worked in the last 6 months. Right now it works here but it doesn't work on SO (Chrome 53.0.2785.116, 64 bit, on Windows 7, if that matters). And there should already be a bug report somewhere (either here or on Meta SO), though I can't find it now. – Fabio Turati Sep 29 '16 at 16:05
  • 1
    I was getting confused with another issue about that graph. So it's possible there is no bug report yet, apart from this. But as I said, this has been around for a long time, so it doesn't depend on the new version of jQuery. Anyway, @Michael, if you want to look into it... Thanks! – Fabio Turati Sep 29 '16 at 16:39
  • 1
    Just realised (via this), that my problem was zoom. All works fine (for me at least) at 100% :) – Cai Oct 1 '16 at 12:06
  • 2
    Holy crap, @Cai, you are right, it's the zoom! That's why sometimes it was working and sometimes not: because I'm using more than one pc, and more than one browser, with different zoom settings for different SE sites. And I thought it was "intermittent"! :-D – Fabio Turati Oct 5 '16 at 15:47
6

Ctrl+Enter in the search box at the top of every page used to open the search results in a new tab. Now it does nothing (Chrome 53, Linux, no userscripts) or opens the search results in the same tab (Firefox 45.3, Linux, no userscripts). Since I haven't change anything on my end recently, I blame jQuery.

6

When I do something that opens an editor, such as clicking on the “edit” button, pressing e, or clicking the 10ker “edit tags” button or pressing t, there's a long time (sometimes >1s) during which subsequent key pressed are interpreted as shortcuts, rather than typing in the text box. For example, quickly typing t a jumps to the answer box then opens the tag editor, instead of opening the tag editor and entering a there, which is what t <pause> a does.

This is with the official Stack Exchange keyboard shortcuts active.

I think, but I'm not completely sure, that this is actually a pre-existing bug (I guess it's doing something asynchronous to enter the editor), but I hardly ever saw the problem before, whereas it's been annoying me all evening today. So this may be a new bug, or it may be a new performance loss.

  • I'm also seeing this on Safari and Firefox, and I also have the impression that the bug was introduced around the same time as the jQuery upgrade. – 200_success Oct 5 '16 at 1:11
5

Every time I click on my custom tabs or go to the home page, Stack Overflow freezes the browser and then I get the following alert:

enter image description here

This is happening in

OS: Ubuntu 15.10 (64 bits)

Browser: Firefox 45.0

While in Chrome 49.0.2623.110

it just goes in a delay of 5~7 seconds while scrolling down / switching view of tabs

Already deleted recent history, cache and cookies


EDIT

I have tested it on Windows 10

Firefox version 50.0b1 (Beta version)

With the same results as above

  • With Custom Tabs, do you mean the new navigation? I'll try on Ubuntu in a bit, but it works fine in Firefox 49 for me :/ if you click "Debug Script", where does it break in the debugger? – Michael Stum Sep 28 '16 at 18:17
  • @MichaelStum yes I mean the new navigation. It seems it's breaking on this method: },"submitFormOnEnterPress":function(e){ in the stub.en.js file – Frakcool Sep 28 '16 at 18:25
  • 3
    Thanks, will investigate closer. – Michael Stum Sep 28 '16 at 18:25
  • 1
    Same same, Chrome 54.0.2840.41 beta-m (64-bit) on Windows 8.1 - never had this issue before. – assylias Sep 29 '16 at 11:28
  • @MichaelStum Have you found anything? I have posted a separate, but possibly related, question: meta.stackexchange.com/questions/285633/… – assylias Oct 20 '16 at 8:32
  • 1
    @assylias from your own question I can say I also have a lot of ignored tags, so probably Michael Stum can get a hint from there, but I have them to be hidden, but the questions with tags on my favorite tags seem to load slow and freeze the browser until it finally paints them in "yellow/orange" in Stack Overflow at least, in other sites where I have no favorite / ignored tags there's no freeze at all – Frakcool Oct 20 '16 at 13:03
  • @MichaelStum is there any workaround for this error? Whenever I enter Stack Overflow I'm still getting the same error as above – Frakcool Dec 2 '16 at 16:22
  • 1
    @Frakcool I believe that I have found a potential cause of this, at least I could reproduce some slowness. I hope to have a performance improvement soon. – Michael Stum Dec 12 '16 at 13:30
  • @MichaelStum thanks, it has something to do with ignored tags, I had about 100+ I think, once I deleted them I got this problem anymore – Frakcool Dec 12 '16 at 14:17
  • @MichaelStum I have added a bounty to my question – assylias Jan 5 '17 at 10:43
4

I visited this post just now via hot network questions and although the sorting option was selected by votes, the posts were ordered incorrectly, and after clicking the "votes" again, they sorted properly. And right while I was writing this, there is 1 more answer posted. Don't know if that's all related but there you go.

4

Tag suggestions are not working after the first tag.

  1. Ask a question.
  2. In the tag textbox, type the first letters of any tag. Observe that there is a tag suggestions popup.
  3. Click on any tag to select the tag. Observe that the completed tag is auto-filled into the textbox.
  4. Type the first letters of a second tag. Observe that there is a tag suggestions popup.
  5. Click on any tag. Observe that auto-fill is no longer working.
  6. Typing anything further in the textbox does not result in the tag suggestion popup.

If the question is posted then edited (thus opening the editing UI again), the second tag can be completed this way. However the third tag will not work in that instance of the edit question UI.


Problem encountered on:

Site: Aviation.SE

Browser: Internet Explorer 10

  • 1
    Will check on IE10 - it seems to be ok for me in Chrome and IE11, will bring up an IE10 machine now. – Michael Stum Sep 28 '16 at 15:19
  • @MichaelStum with Edge and IE11 being latest versions, is IE10 still fully supported? – Shadow Sep 28 '16 at 19:28
  • 1
    @ShadowWizard Edge and Internet Explorer are technically two different browsers, and we support two versions back. So we'll try to. – Michael Stum Sep 28 '16 at 20:49
  • @MichaelStum Just FYI, you can run IE10 in IE11: stackoverflow.com/questions/18588769/… – Gruber Sep 29 '16 at 18:29
  • @Gruber from my own experience, I have found that running IE in emulated mode is not accurate on rare occasions. Generally it works though. – kevin Sep 29 '16 at 18:34
  • Can repro on IE10 (Windows 8) on Aviation. Works on SO. Checking for the root cause. – Michael Stum Sep 30 '16 at 22:27
  • @MichaelStum Any update on this one? As of 1 Nov, this issue still exists. Also experienced a few other sites as well. – kevin Nov 1 '16 at 12:17
  • @kevin Sorry, was out for a while, I'll resume looking into stuff in this thread hopefully by next week. – Michael Stum Nov 8 '16 at 22:12
  • 1
    Just a heads up, I found the cause of this, but are still looking for a solution (An event isn't bubbling under some circumstances caused by something completely different) – Michael Stum Dec 12 '16 at 11:40
3

Issues in the top nav reputation scroll (Chrome Version 53.0.2785.116 64-bit, Mac OS X 10.11.6):

1. Can't scroll using the grey rail

enter image description here

2. When you collapse reputation for specific day the scroll rail disappears

enter image description here

  • Can't reproduce this, using Chrome 53.0.2785.92 and Ubuntu 16.04 – Alter Lagos Sep 30 '16 at 3:20
  • I also cannot repro using Chrome 53.0.2785.116 m (on Windows) – DavidG Sep 30 '16 at 15:30
  • No repro either on Firefox. – André Borie Sep 30 '16 at 17:38
1

On the reputation tab in profile, if there is any reputation change since your last visit, the source from where you got the reputation shows up by DOWN arrow there, the bug is, it is showing two times the same sources if there is reputation gain from the same answer.

Once you reload the page, your reputation change since last visit becomes 0, and the bug can not be seen anymore.

0

This answer was at -3 and was translucent. I clicked the upvote and received a red box with a generic error (something of the order "There was an error. Please try again."). But my view of the answer showed -2, as if my upvote had been accepted.

So I refreshed the page and saw my upvote was not accepted and the answer was still at -3. I clicked the upvote again and this time it worked.

  • Refresh the page and retry. – TuxCrafting Sep 30 '16 at 16:17
  • 1
    @TùxCräftîñg - ummm, I did. That's in my post above. But the bug is that I saw the error in the first place, not that it eventually worked after refresh. – devlin carnate Sep 30 '16 at 16:43
-1

The reputation graph on the Activity tab does not handle the browser zoom properly on the latest Chrome on Windows.

If I set the zoom to 110%, and click on the graph, the blue area doesn't move at all, as if the clicks were ignored. If I set the zoom to 100%, it works fine.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .