4

A very recent change that has been deployed is preventing me from asking new questions or editing existing questions using Internet Explorer 11. (Yes, it is a supported browser.)

When asking a new question or editing an existing one, the tag bar appears in plain text, and the submit button is always disabled.

enter image description here

Why is this happening?

Improve this question
4
  • 1
    See also: meta.stackoverflow.com/questions/371290/… (appears to also affect Safari, though I can't say which version(s)) Commented Jul 19, 2018 at 19:36
  • 1
    I'm not 100% sure but I think in tageditornew.en.js this line needs fixing: editor.addClass("s-input").css({paddingTop: 0, paddingTop: 0}); the double paddingTop is not allowed. Commented Jul 19, 2018 at 19:43
  • yep, that's it @rene Commented Jul 19, 2018 at 19:53
  • blame a relaxed jslint rule ... Commented Jul 19, 2018 at 20:00

1 Answer 1

Reset to default
5

As rene pointed out in the comments, this appears to have been triggered by a newly-added bit of code in the tag editor which tries to set the same property twice in a single call.

That's... likely a typo; I changed one of the paddingTop properties to paddingBottom and the page loads on IE just fine.

This fix should now be live.

Improve this answer
5
  • Correct CSS is "padding-top", not "paddingTop" - no? Unless CSS changed drastically since I learned the basics and it allows JS style syntax? Anyway, guess jQuery changes it by itself otherwise it wouldn't be working at all, just neat picking here. :-) Commented Jul 19, 2018 at 21:39
  • @ShadowWizard The DOM style properties JS interacts with are camel case. Commented Jul 19, 2018 at 21:43
  • CSS also doesn't care about duplicate rules, @Shadow. The jQuery call - .css({style properties}) - takes an object, and JS sometimes does mind duplicate object properties. Note also that while the CSS property is padding-top, the equivalent DOM property is paddingTop - not that this is relevant. Commented Jul 19, 2018 at 21:44
  • Well, I'm using that .css({style properties}) myself sometimes, but always gave the "CSS case", not JS camelCase. Admit that I never looked into it, just seemed like the proper way. Anyhow... thanks for the quick fix, on behalf of all the IE11 users! :) (Which I'm not among them.) Commented Jul 19, 2018 at 21:54
  • @ShadowWizard jQuery allows you to pass properties either as camelCase or as in CSS. It then internally converts the names into camelCase. Commented Jul 20, 2018 at 8:26

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.