1

I have an answer for the question, but the question was closed because too narrow geographically. I think this is a broadly applicable question and should be reopened; the problem is a bug in the popular chrome to phone extension that messes up the JS on pages you view.

I would just leave a comment on the question, but I'm brand new here and don't have any rep.

If nobody will open it, can someone at least post in the comments section of that question that he should try disabling chrome to phone. There are documented probs with that extension, and my JS worked when I did that. Here's a link to the probs with chrome to phone: https://code.google.com/p/chrometophone/issues/detail?id=316.

Thanks.

|improve this question
  • 1
    How is Chrome to Phone related here? – Andrew Barber Jun 25 '13 at 1:56
  • Then post it on the comment. – Old Checkmark Jun 25 '13 at 1:58
  • @doubleDown Rep limit. – Undo - Reinstate Monica Jun 25 '13 at 1:59
  • 1
    Reason I ask: if a bug in Chrome to Phone is the cause here, the issue is definitely too localized. I'll post your link, though. – Andrew Barber Jun 25 '13 at 2:01
  • 2
    Oops missed that bit about rep. Btw why was there an appeal to Jon Skeet in javaL's final comment? – Old Checkmark Jun 25 '13 at 2:05
8

No, it is too localized.

Not because it is only applicable to a specific moment in time or geography, but rather that it's too localized in that no one will ever have that exact code & problem again. Think about it - it's basically 'I have this error and this code. What's wrong?'

That's the very definition of too localized.

|improve this answer
  • I agree that the question as written is too localized, but that's only bc the asker thinks there's a problem in his/her code. There isn't. The point of the question is, "hey, why is my JS not working in chrome but it is in all these other browsers, and btw I'm getting this specific error error." I was having the same prob with the same error, and my fix worked. – Matt Jun 25 '13 at 1:57
  • @Matt So the question is too localized. Therefore, it needs to be closed in its current state. Feel free to suggest an edit to improve it, though! – Undo - Reinstate Monica Jun 25 '13 at 1:58
  • "no one will ever have that exact code & problem again." Except that the person answering has also seen that problem, and has a fix for it. – Danack Jun 25 '13 at 2:05
  • 1
    @Danack Hyperbole :) Would you say that it appeals to the broader audience of the Interwebs? – Undo - Reinstate Monica Jun 25 '13 at 2:06
  • @Danack If you agree with the OP, go cast a reopen vote - who am I to stop you? – Undo - Reinstate Monica Jun 25 '13 at 2:07
  • 1
    Oh, no thanks. It's still a rubbish question. I'm still looking forawrd to 'on hold, unclear what you're asking' as the original question just has "it doesn't work in chrome" as its 'question'. – Danack Jun 25 '13 at 2:09
  • @Danack You and me both. – Undo - Reinstate Monica Jun 25 '13 at 2:09

You must log in to answer this question.

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