[Webkit-unassigned] [Bug 93473] New: Web Inspector: The front-end should provide the position in original source file when set a breakpoint

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=93473

           Summary: Web Inspector: The front-end should provide the
                    position in original source file when set a breakpoint
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: peter.wang at torchmobile.com.cn
                CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    bweinstein at apple.com, apavlov at chromium.org,
                    loislo at chromium.org


I'd like to discuss here, should we provide the the position in original source file when set a breakpoint. For example, a JS statement like this:
[space][space][space]var[space]a=1;
The position in original source file is (0,3), but now front-end send (0,0) when set a breakpoint, the heading spaces are removed.
To accommodate it, JSC has to add code to meet the same rules of removing leading space.

If we just provide the original position of a breakpoint, we can make JS engine and front-end independent, so that when front-end change the Formatter or support feature like "Pretty Print", the JS engine is kept unchanged.

It's my personal suggestion. I'd like to discuss.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.