Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

OK so today I started to hit edit on peoples questions and I notice:

  • The toolbar on the top is first disabled.
  • Then the preloader (same one that shows for the tags etc) shows up.


The page kinda reloads and my caret gets places in the title.

So everytime I hit edit, I start editing the question and a second or two later my caret is in the title box and whatever I just typed replaces the title.

This is very annoying as I've had to return to the question and then hit edit, wait for the loading and then start editing quite a few times, till I got frustrated and decided to post here.

Might not be too useful but here is a screenie anyway : enter image description here

Note, how the toolbar is disabled.

I'm on Google Chrome 10 + Windows 7 x64

share|improve this question
whopsies, updated question =) – gideon Apr 13 '11 at 16:47
Right-clicking, selecting "inspect element" anywhere on the page, will get you the web inspector. Opening its Network tabsheet and then refreshing the page might show some resource that fails to load, or is extremely slow to load? (No issues in Chrome 10 on a Mac, here.) – Arjan Apr 13 '11 at 16:51
oh? I thought this was a new feature. Post-loading the edit bar for some vague reason. I'll do more research and get back here. – gideon Apr 13 '11 at 16:52
Might sound silly - are you logged in when it happens? – Shadow Wizard Apr 13 '11 at 17:25
@shadow yes I am logged in. like I said, me thought the preloader was by design.. will try on my laptop tomrw morning and add an update.. – gideon Apr 13 '11 at 18:33
Weird, the only time I see the "preloader" is when focusing the edit area while not logged in then it's loading the "Thanks for contributing an answer to Stack Overflow! This is a Q&A site,..." message however it does not set focus to the title. – Shadow Wizard Apr 13 '11 at 18:44
@giddy, maybe it helps investigating: do you have the same issue when editing other people's answers? And what about editing your own posts? – Arjan Apr 14 '11 at 7:00
up vote 3 down vote accepted

This is not supposed to happen; the loading of the editor being delayed until the text box is focused should only happen for anonymous users when viewing a question.

The way this is implemented is that the file wmd.js just isn't included in the page itself; the JavaScript then checks if the function editorReady exists (this function is provided by wmd.js). Only if this function isn't there, the whole "disabled" thing happens.

My guess is that there's a bug in Chrome 10 that causes the check for editorReady to happen before that object is available (which shouldn't happen, based on the order of stuff in the page).

So unless someone can reproduce this with a released browser, I'm inclined to consider this a bug in a beta browser. Never mind that – the fact that Chrome 10 was released went past me somehow. I'm still sure this is a Chrome bug, but since it's an officially supported browser, we'll investigate.

share|improve this answer
based on the order of stuff in the page — unfortunately no time to investigate right now (and I am NO expert!), but in 2008 IE8 introduced a scary parallel script loading. I've never investigated what happens when such external script includes code that is (to be) executed right away. (Like code outside a function definition.) Maybe Chrome 10 has introduced some parallel thingy too, and has somehow taken it a step further? That said, I do NOT have this issue when logged in, nor in incognito mode, in Chrome on a Mac. – Arjan Apr 13 '11 at 22:59
@Arjan: Yeah, that's my thought as well. And yes, I've seen similar problems in IE; e.g. if you trigger an event at the end of some JavaScript file, the stuff from said JS file isn't yet available to the handler bound to that event; you have to go through a 1ms timeout. Annoying. – balpha Apr 13 '11 at 23:45
So this is status-norepro for me and several people I know on Chrome 10 ... – jcolebrand Apr 13 '11 at 23:47
I want a diamond too! – Arjan Apr 14 '11 at 11:53
=( jeez I'm at work on my laptop (Win7+Chrome10) now and its all good! The edit toolbar appears ^pop^, neatly, just like before. I haven't rechecked at the desktop PC I was on last night! @balpha sorry for the trouble. I thought it was some new fangled feature and when it got just t0o annoying I slapped it here! =) – gideon Apr 14 '11 at 13:44

You must log in to answer this question.

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