A second change I would like to make is to eliminate the "liveness" of
the sheet.. With support coming online for both injected user scripts
and user stylesheets, I expect that a better way to deal with this is
to have a Develop menu item (or inspector item) to reload all user
content.
Automatic liveness seems like a non-goal other than for user
stylesheet *developers*, and having to examine local files every time
you open a new tab/window just to support developers seems like the
wrong trade-off to me. That this is happening in the engine process
can't be good for Chrome either, and going forward we should be
discouraging file accesses like this from being done inside WebCore.
dave
([email protected])
On Sep 4, 2009, at 2:52 PM, Tor Arne Vestbø wrote:
On 9/4/09 9:47 PM, David Hyatt wrote:
Right now the user stylesheet location is stored as a URL. This is
based off ancient history, namely that we happened to store the
preference this way on Mac. Even though Safari only allows you to
pick
local files from its UI for user stylesheets, the preference itself
is a
URL. Because of this, the current code is making an assumption that
remote URLs should be allowed to work as user stylesheets. On Mac
and Qt
only, we have a UserStyleSheetLoader object that is dealing with
remote
URLs. Other platforms seem to just not support this.
I would like to eliminate this object on all platforms.
Sounds good.
Tor Arne
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
