<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Can't edit JS resource"
href="https://bugs.webkit.org/show_bug.cgi?id=161418#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Can't edit JS resource"
href="https://bugs.webkit.org/show_bug.cgi?id=161418">bug 161418</a>
from <span class="vcard"><a class="email" href="mailto:dcrousso+webkit@gmail.com" title="Devin Rousso <dcrousso+webkit@gmail.com>"> <span class="fn">Devin Rousso</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=161418#c4">comment #4</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=161418#c2">comment #2</a>)
> > Users should only be able to edit local (file:///) JavaScript resources. I
> > don't think we've ever been able to edit arbitrary JavaScript resources.
>
> I think we should change that. Most decently sized websites aren't developed
> using file scheme. Of the top of my head, there are two common use cases:
>
> 1. Local development server running on <a href="http://localhost:1234">http://localhost:1234</a> or
> <a href="http://myapp.dev">http://myapp.dev</a>.
> 2. Remote development server with locally mounted partition (via SSHFS).</span >
I agree that local development could benefit from this, but what would editing the resource do (will the new code written ever be executable)? How about editing a non-local resource? How do we even distinguish whether the resource is local?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>