35451 2010-02-26 14:06:35 -0800 Inspector and debugger line numbers are different between Safari and Chrome 2014-01-28 14:01:44 -0800 1 1 1 Unclassified WebKit Web Inspector (Deprecated) 528+ (Nightly build) PC OS X 10.5 RESOLVED INVALID P2 Normal --- 1 jparent webkit-unassigned bburg pfeldman pmuellr oldest_to_newest 194278 0 jparent 2010-02-26 14:06:35 -0800 For multi-line statements, Safari uses the line number from the last line, and Chrome uses the line number from the first line. For example, given the following: <html> <head> <script> throw('which line number am i?' + 'I start on line 4' + ' but end on line 6'); </script> </head> <body> </body> </html> Safari will list the error and stop the debugger pointing to line 6, whereas chrome will point to line 4. My intuition is that the first line is more what developers would expect. 198290 1 pmuellr 2010-03-10 13:10:15 -0800 This is surely a V8 vs JSC issue, no? Change component? Since this type of behaviour - line number reporting for exceptions - is totally unspec'd w/r/t ECMAScript, it's not clear which one is "right", but I agree stopping at the "first line of the statement" is more intuitive. It would also be nice to try this in FF; I tried it but couldn't get FB to generate ANY line number information. But my FB foo is weak these days, maybe I did something wrong.