[Webkit-unassigned] [Bug 22927] New: Using spaces for indent in Ext/Javascript code causes all Javascript execution to fail silently
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Dec 18 16:56:56 PST 2008
https://bugs.webkit.org/show_bug.cgi?id=22927
Summary: Using spaces for indent in Ext/Javascript code causes
all Javascript execution to fail silently
Product: WebKit
Version: 525.x (Safari 3.2)
Platform: PC
OS/Version: Windows XP
Status: UNCONFIRMED
Severity: Critical
Priority: P2
Component: JavaScriptCore
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: brian-webkit at vfive.com
I have some Javascript that uses Ext components. The indenting was done with
spaces. Loading the document in Firefox/IE works properly; the code is valid
and there are no syntax issues associated with it. Both Webkit browsers Safari
and Chrome failed to execute the Javascript and failed to throw an error.
Simply nothing happened. In fact, putting a <script>alert('hello');</script>
in the body didn't even execute.
It turns out we fixed the problem by converting spaces to tabs. Nothing else.
Suddenly it worked. Simply regexp'ing [ ]{4} to tab fixed the issue. We can't
understand it.
I'm attaching a diff between the two files. I'm also including the broken.html
and working.html files for your review. There are going to be a couple of
different lines between the HTML files because I generated one from our
still-broken staging server and another from my working local copy but aside
from some IDs and whatnot, they should be identical. The key difference is the
spaces vs. tabs for indents.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list