August 2009 - webkit-dev - lists.webkit.org

Handling Ignorable Text in a Renderer
by Alex Milowski 26 Aug '09

26 Aug '09

In certain MathML constructs (e.g. mfenced) there are a number of child elements that make up the construct and need to be rendered. Any text between those child elements should be ignored. In fact, non-whitespace text in the wrong place is most certainly incorrect but something that can be recovered from. I don't want to remove the text from the DOM nodes but I need to keep the RenderText instances from being created or displayed. What is the correct way to do this? I've been trying to handle this in the renderer but it seems like that is really too late. I though about changing the attach method to exclude such ignorable text. -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics

2 3

Re: [webkit-dev] Building QtWebkit on Mac OSX 10.5.6 with Qt 4.5
by Garth Dahlstrom 26 Aug '09

26 Aug '09

Hi All, Picking up on this thread from April ( http://lists.macosforge.org/pipermail/webkit-dev/2009-April/thread.html#7296) I'm in a simliar spot as Husam; on OSX 1.5.8 w/ MacPorts Qt 4.5.2. I made it a little further by overriding the mkspec to be macx-g++, so I'm no longer stuck at the XCode/XProj generation stuff. However I now have a problem that my $QTDIR/include directory is not being picked up. If someone could suggest how I can inject the ${QTDIR}/include into the build environment, I would be grateful for the assist. Cheers, -G Here is the truncated compile output: [649] ged@gMacBook:~/mnt$ WEBKITOUTPUTDIR=`pwd`/qtbuild WebKit/WebKitTools/Scripts/build-webkit --qt --qmake=qmake-4.5 --makeargs="-j3 -s" -spec macx-g++ --no-video --debug Calling 'qmake-4.5 -r -spec macx-g++ DEFINES+=ENABLE_VIDEO=0 OUTPUT_DIR=/Users/ged/mnt/qtbuild/Debug /Users/ged/mnt/WebKit/WebKit.pro CONFIG-=release CONFIG+=debug' in /Users/ged/mnt/qtbuild/Debug Reading /Users/ged/mnt/WebKit/WebCore/WebCore.pro [/Users/ged/mnt/qtbuild/Debug//WebCore] Project MESSAGE: Building QtWebKit as a framework, as that's how Qt was built. You can Project MESSAGE: override this by passing CONFIG+=webkit_no_framework to build-webkit. /Developer/Tools/Qt/rcc: File does not exist '../../../WebKit/WebCore/inspector/front-end/WebKit.qrc' /Developer/Tools/Qt/rcc: File does not exist '../../../WebKit/WebCore/WebCore.qrc' Reading /Users/ged/mnt/WebKit/JavaScriptCore/jsc.pro[/Users/ged/mnt/qtbuild/Debug//JavaScriptCore] Reading /Users/ged/mnt/WebKit/WebKit/qt/QtLauncher/QtLauncher.pro [/Users/ged/mnt/qtbuild/Debug//WebKit/qt/QtLauncher] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/tests.pro[/Users/ged/mnt/qtbuild/Debug//WebKit/qt/tests] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebframe/qwebframe.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebframe] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebpage/qwebpage.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebpage] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebelement/qwebelement.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebelement] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebhistoryinterface/ qwebhistoryinterface.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebhistoryinterface] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebplugindatabase/ qwebplugindatabase.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebplugindatabase] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebview/qwebview.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebview] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/qwebhistory/qwebhistory.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//qwebhistory] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/benchmarks/painting/ tst_painting.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//benchmarks/painting] Reading /Users/ged/mnt/WebKit/WebKit/qt/tests/benchmarks/loading/ tst_loading.pro[/Users/ged/mnt/qtbuild/Debug/WebKit/qt/tests//benchmarks/loading] Reading /Users/ged/mnt/WebKit/WebKitTools/DumpRenderTree/qt/DumpRenderTree.pro [/Users/ged/mnt/qtbuild/Debug//WebKitTools/DumpRenderTree/qt] Reading /Users/ged/mnt/WebKit/WebKitTools/DumpRenderTree/qt/ImageDiff.pro [/Users/ged/mnt/qtbuild/Debug//WebKitTools/DumpRenderTree/qt] Reading /Users/ged/mnt/WebKit/WebKitTools/DumpRenderTree/qt/TestNetscapePlugin/TestNetscapePlugin.pro [/Users/ged/mnt/qtbuild/Debug//WebKitTools/DumpRenderTree/qt/TestNetscapePlugin] In file included from ../../../WebKit/JavaScriptCore/wtf/unicode/Unicode.h:29, from ../../../WebKit/JavaScriptCore/pcre/pcre.h:45, from ../../../WebKit/JavaScriptCore/pcre/pcre_internal.h:82, from ../../../WebKit/JavaScriptCore/pcre/pcre_exec.cpp:46: ../../../WebKit/JavaScriptCore/wtf/unicode/qt4/UnicodeQt4.h:26:17: error: QChar: No such file or directory ../../../WebKit/JavaScriptCore/wtf/unicode/qt4/UnicodeQt4.h:27:19: error: QString: No such file or directory .... lots more of the same .... __ --- == __/ t.O ==-- http://stacktrace.org/

1 3

How to handle Array types in IDL files?
by Drew Wilson 26 Aug '09

26 Aug '09

I'm trying to update MessageEvent to match the current HTML5 spec. Currently, MessageEvent has two references to MessagePort: readonly attribute *MessagePort messagePort*; void initMessageEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString dataArg, in DOMString originArg, in DOMString lastEventIdArg, in DOMWindow sourceArg, *in MessagePort messagePort*); MessageEvent now needs to support an array of MessagePorts. I had planned to provide a custom getter for the messagePort attribute and change initMessageEvent to be custom as well, resulting in this: readonly attribute [CustomGetter] *Array ports*; [Custom] void initMessageEvent(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString dataArg, in DOMString originArg, in DOMString lastEventIdArg, in DOMWindow sourceArg, *in Array messagePorts*); My custom JS handlers could map between JSArray and the native WebCore collection used by the impl class. I'm not certain whether this is the right approach for the objc bindings, however - in fact, the generated code for DOMMessageEvent.mm contains "#import Array.h" and "#import DOMArrayInternal.h", neither of which exist. What do people suggest here? I'm not certain how this should be exposed for ObjC. Other classes (like Clipboard.idl) that use Array don't seem to have objc bindings, but I don't think that's an option for MessageEvent. -atw

4 6

Rendering Help with MathML for mfenced
by Alex Milowski 26 Aug '09

26 Aug '09

I'm working on a MathML implementation for WebKit and I've had some success but I'm a bit stuck with the approach I'm using for mfenced. This element wraps a sequence of expressions in brackets (or some other paired symbol). The brackets need to scale to the maximum height of the contained objects. I decided that the best approach was to let the container layout the contents and then inspect the box heights. This approach has worked well when you render MathML via Javascript. The problem I'm having is that I adjust the opening and closing fencing symbols via the font size. This causes their box size to change but the whole construct (which is an inline-block container) doesn't get reflowed. As such, the opening fence (defaults to a '{' bracket) overflows onto the first item in the fenced content. What I want to do is tell the renderer that the contents all need to be reflowed because the size of the first and last object has changed. I haven't succeeded in doing this yet although the resizing of the open and close fencing does work quite well. Any ideas as to what I need to do would help. Here's the layout code for the rendered for the mfenced element: void RenderFenced::layout() { if (isEmpty()) { makeFences(); } RenderBlock::layout(); RenderBoxModelObject *open = (RenderBoxModelObject *)firstChild(); RenderBoxModelObject *close = (RenderBoxModelObject *)lastChild(); int maxHeight = 0; RenderObject *current = open->nextSibling(); while (current!=close) { if (current->isBoxModelObject()) { RenderBoxModelObject *box = (RenderBoxModelObject *)current; if (box->offsetHeight()>maxHeight) { maxHeight = box->offsetHeight(); } } current = current->nextSibling(); } if (maxHeight>0) { bool doLayoutAgain = false; if (open->offsetHeight()<maxHeight) { const FontDescription oldDesc = open->style()->font().fontDescription(); FontDescription *desc = new FontDescription(); desc->setIsAbsoluteSize(true); desc->setGenericFamily(oldDesc.genericFamily()); desc->setWeight(oldDesc.weight()); desc->setSmallCaps(oldDesc.smallCaps()); desc->setItalic(oldDesc.italic()); desc->setSpecifiedSize(maxHeight); desc->setComputedSize(maxHeight); open->style()->setFontDescription(*desc); open->style()->font().update(open->style()->font().fontSelector()); open->setNeedsLayoutAndPrefWidthsRecalc(); doLayoutAgain = true; } if (close->offsetHeight()<maxHeight) { const FontDescription oldDesc = close->style()->font().fontDescription(); FontDescription *desc = new FontDescription(); desc->setIsAbsoluteSize(true); desc->setGenericFamily(oldDesc.genericFamily()); desc->setWeight(oldDesc.weight()); desc->setSmallCaps(oldDesc.smallCaps()); desc->setItalic(oldDesc.italic()); desc->setSpecifiedSize(maxHeight); desc->setComputedSize(maxHeight); close->style()->setFontDescription(*desc); close->style()->font().update(open->style()->font().fontSelector()); close->setNeedsLayoutAndPrefWidthsRecalc(); doLayoutAgain = true; } if (doLayoutAgain) { setNeedsLayout(true); RenderObject *current = firstChild(); while (current) { current->setNeedsLayoutAndPrefWidthsRecalc(); current = current->nextSibling(); } layout(); } } } -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics

1 1

How to Adjust scrollPosition after Frame::setZoomFactor
by Nitin Mahajan 26 Aug '09

26 Aug '09

HI! I am zooming the contents of a WebFrame by calling QWebFrame::setZoomFactor. However after the zooming operation the scrollPosition remains same as before zooming. Hence, I cannot see the same content in the viewport after zooming. Can somebody help me understand, how to determine the correct post zooming scrollPosition so that I can call setScrollPosition with appropriate args and I can see the same content in the view port even after zooming? regards -Nitin Get your new Email address! Grab the Email name you've always wanted before someone else does! http://mail.promotions.yahoo.com/newdomains/aa/

1 0

Bugzilla Maintenance: Tue Aug 24, 6-7pm
by William Siegrist 26 Aug '09

26 Aug '09

Bugzilla will be down for maintenance from 6pm to 7pm tomorrow evening. We are migrating the backend database to postgresql, so no user-visible changes should result. We will make announcements in irc as usual. Thank you. -Bill

1 1

r45939 broke my workflow
by Geoffrey Garen 25 Aug '09

25 Aug '09

Hi. r45939 broke my workflow. Here's the related bugzilla bug: https://bugs.webkit.org/show_bug.cgi?id=26999 . Old "Roll out a patch" workflow: cd JavaScriptCore svn-create-patch > patch.txt svn-unapply patch.txt Old "Roll in a patch" workflow: cd JavaScriptCore svn-apply patch.txt These old ways of doing things no longer work because svn-apply and svn-unapply don't match svn-create-patch's new behavior of changing to the WebKit root directory if you're currently working in a WebKit subdirectory. Here's an example command-line interaction: > ~/webkit/WebKitTools/Scripts$ svn-create-patch > ro.txt > ~/webkit/WebKitTools/Scripts$ svn-unapply !$ > svn-unapply ro.txt > can't find file to patch at input line 5 > Perhaps you used the wrong -p or --strip option? > The text leading up to this was: > -------------------------- > |Index: WebKitTools/Scripts/webkitdirs.pm > |=================================================================== > |--- WebKitTools/Scripts/webkitdirs.pm (revision 47638) > |+++ WebKitTools/Scripts/webkitdirs.pm (working copy) > -------------------------- > File to patch: ^C'WebKitTools/Scripts' is not a directory at ./svn- > unapply line 315, <> line 9. I tried to ignore this for a while, but it's really causing problems for me and at least one other WebKit developer. Should we revert r45939? Is there an easy fix to svn-apply and svn-unapply that you can make? Thanks, Geoff

10 15

Building a simple web crawler with webkit
by Dan 25 Aug '09

25 Aug '09

Hi list, Massive apologies in advance for this being both the wrong place to ask, and a very vague question... but, does anyone have any general guidance as to where I'd start with webkit if I wanted to build a headless web client, along the lines of a crawler / bot, on top of it? Would I be best to use individual parts of the code, or implement a browser and hide the UI side of it? I'm not much of a C++/ObjC developer, so I can't begin to expect to be able to do this immediately, but any tips you can give would be greatly appreciated. Thank you! Dan Cryer

2 1

Building release on Windows Vista
by Anton Muhin 25 Aug '09

25 Aug '09

Dear WebKit gurus, is it possible to build WebKit on Windows Vista in Release configuration? Both build from Cygwin and VS dies with: c:\WebKit\WebKit\WebKitBuild\lib\WebCore.lib : fatal error LNK1106: invalid file or disk full: cannot seek to 0x44DA4146 Clean build (wiping off WebKitBuild) has been tried. I git clone'ed rather recent version of WebKit (something two or three hours long from the time this message has been sent). Debug could be built fine from cygwin. Any hints are most appreciated. tia and yours, anton.

3 2

Re: [webkit-dev] webkit-dev Digest, Vol 51, Issue 26
by ravi swami 25 Aug '09

25 Aug '09

Is SquirrelFish Extreme included in latest versions of webkit? On 8/24/09, webkit-dev-request(a)lists.webkit.org <webkit-dev-request(a)lists.webkit.org> wrote: > Send webkit-dev mailing list submissions to > webkit-dev(a)lists.webkit.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > or, via email, send a message with subject or body 'help' to > webkit-dev-request(a)lists.webkit.org > > You can reach the person managing the list at > webkit-dev-owner(a)lists.webkit.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of webkit-dev digest..." > > > Today's Topics: > > 1. Re: LayoutTest results choose from which folder? (Dirk Pranke) > 2. Re: LayoutTest results choose from which folder? (Dan Bernstein) > 3. Re: Security advice for linux browsers based on WebKit > (Gustavo Noronha Silva) > 4. Re: Security advice for linux browsers based on WebKit > (Adam Barth) > 5. Re: Security advice for linux browsers based on WebKit > (Gustavo Noronha Silva) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 23 Aug 2009 11:28:37 -0700 > From: Dirk Pranke <dpranke(a)chromium.org> > To: Dan Bernstein <mitz(a)apple.com> > Cc: WebKit-Dev <webkit-dev(a)lists.webkit.org> > Subject: Re: [webkit-dev] LayoutTest results choose from which folder? > Message-ID: > <3726d1bf0908231128t470f0f29n7fab1a791dcbea05(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > >> Hi Chris, >> In layout test results, we make the latest Mac OS X version the rule, and >> earlier versions the exception. Tiger will look for results in mac-tiger >> first, then in mac-leopard, then in mac-snowleopard, then in mac, then >> finally in cross-platform results. Leopard will begin the search in >> mac-leopard, continue to mac-snowleopard, then mac, the cross-platform. >> As you can see, there are no expected results in mac-snowleopard (other >> than >> the ones you just added), because it?s the latest Mac OS X version. We >> will >> only start putting expected results in mac-snowleopard when the ?latest? >> version (for which we put results in mac) will be something different. >> You should put the expected results for Snow Leopard in platform/mac (or, >> if >> they are cross-platform, alongside the test), and you should put the >> results >> for Leopard and earlier in platform/mac-leopard. >> ?Dan > > Does this imply that if you've moved results from 'platform/mac' to > 'platform/mac-leopard' when you switched from 10.5 to 10.6? (Since, > presumable, some results that were in platform/mac were actually > specific to 10.5?) > > I would've expected a different model, where if the output differed by > version, then you had results in 'mac-leopard' and 'mac-snowleopard', > and the presence in 'mac' meant it should be the same across both > (this was the approach I was planning to use for Chromium, which is > just starting to run into this problem with XP/Vista/Win 7). I can see > some advantages to your approach, but it seems more confusing in the > long run. > > -- Dirk > > > ------------------------------ > > Message: 2 > Date: Sun, 23 Aug 2009 12:23:09 -0700 > From: Dan Bernstein <mitz(a)apple.com> > To: Dirk Pranke <dpranke(a)chromium.org> > Cc: WebKit-Dev <webkit-dev(a)lists.webkit.org> > Subject: Re: [webkit-dev] LayoutTest results choose from which folder? > Message-ID: <ECC55AB8-992E-4708-B1FF-1E4E29123AED(a)apple.com> > Content-Type: text/plain; charset=windows-1252; format=flowed; > delsp=yes > > > On Aug 23, 2009, at 11:28 AM, Dirk Pranke wrote: > >>> Hi Chris, >>> In layout test results, we make the latest Mac OS X version the >>> rule, and >>> earlier versions the exception. Tiger will look for results in mac- >>> tiger >>> first, then in mac-leopard, then in mac-snowleopard, then in mac, >>> then >>> finally in cross-platform results. Leopard will begin the search in >>> mac-leopard, continue to mac-snowleopard, then mac, the cross- >>> platform. >>> As you can see, there are no expected results in mac-snowleopard >>> (other than >>> the ones you just added), because it?s the latest Mac OS X version. >>> We will >>> only start putting expected results in mac-snowleopard when the >>> ?latest? >>> version (for which we put results in mac) will be something >>> different. >>> You should put the expected results for Snow Leopard in platform/ >>> mac (or, if >>> they are cross-platform, alongside the test), and you should put >>> the results >>> for Leopard and earlier in platform/mac-leopard. >>> ?Dan >> >> Does this imply that if you've moved results from 'platform/mac' to >> 'platform/mac-leopard' when you switched from 10.5 to 10.6? (Since, >> presumable, some results that were in platform/mac were actually >> specific to 10.5?) > > Yes, when the expected results of an existing test change under a new > version of Mac OS X, legacy expected results are moved from platform/ > mac to platform/mac-<last version with legacy behavior> and current > expected results are put in platform/mac. > <http://trac.webkit.org/changeset/47052 > > is an example. > >> I would've expected a different model, where if the output differed by >> version, then you had results in 'mac-leopard' and 'mac-snowleopard', >> and the presence in 'mac' meant it should be the same across both >> (this was the approach I was planning to use for Chromium, which is >> just starting to run into this problem with XP/Vista/Win 7). > > Having platform/mac represent ?latest and future versions of Mac OS X? > means that when the next version appears, there is no need to do > anything with tests whose results in the new version are the same as > in the previous version. This model is analogous to how version- > checking macros are used in WebKit code, by making exceptions for the > past, not for the present: there is no BUILDING_ON_<latest version> > macro. > >> I can see >> some advantages to your approach, but it seems more confusing in the >> long run. > > I hope my explanation clears up the confusion. > > ?Dan > > ------------------------------ > > Message: 3 > Date: Mon, 24 Aug 2009 01:02:22 -0300 > From: Gustavo Noronha Silva <gns(a)gnome.org> > To: webkit-dev(a)lists.webkit.org > Subject: Re: [webkit-dev] Security advice for linux browsers based on > WebKit > Message-ID: <1251086542.6026.31.camel(a)goiaba.horta> > Content-Type: text/plain > > On Sat, 2009-08-22 at 22:05 -0700, Adam Barth wrote: >> which disables this behavior. For legacy reasons, we default this >> setting to "true," but I'd like to encourage to use the "false" >> setting by default in your browser, especially if your browser runs on >> Linux. >> >> This issue is particularly important on Linux because many Linux users >> use a network file system, such as AFS or NFS, which maps the entire >> world into the local file system. For example, if I made my home >> directly world-readable, it's quite likely that I would be able to >> control this URL on your user's machines: > > I notice that WebKitGTK+ disables this by default, good =). > > I think, though, that the AFS/NFS issue you mention is more general and > shouldn't be a motivating factor. We have many GNU/Linux users not in > corporate networks, these days, as well, and I think we should not be > designing everything for big installations (those usually have admins > who can worry about this kind of issue). > > Also, it looks like you can access windows shares using > file://server/folder/file.html, so this doesn't seem to be UNIX-specific > in any way. I also bet Mac can be made to use NFS, and AFS, so, again, I > fail to see this as particularly important on non-Mac UNIX-likes. > > See you, > > -- > Gustavo Noronha Silva <gns(a)gnome.org> > GNOME > > > > ------------------------------ > > Message: 4 > Date: Sun, 23 Aug 2009 21:30:13 -0700 > From: Adam Barth <abarth(a)webkit.org> > To: Gustavo Noronha Silva <gns(a)gnome.org> > Cc: webkit-dev(a)lists.webkit.org > Subject: Re: [webkit-dev] Security advice for linux browsers based on > WebKit > Message-ID: > <7789133a0908232130r44ef4956u4bc59c0aeba19f02(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Sun, Aug 23, 2009 at 9:02 PM, Gustavo Noronha Silva<gns(a)gnome.org> wrote: >> On Sat, 2009-08-22 at 22:05 -0700, Adam Barth wrote: >>> which disables this behavior. ?For legacy reasons, we default this >>> setting to "true," but I'd like to encourage to use the "false" >>> setting by default in your browser, especially if your browser runs on >>> Linux. >>> >>> This issue is particularly important on Linux because many Linux users >>> use a network file system, such as AFS or NFS, which maps the entire >>> world into the local file system. ?For example, if I made my home >>> directly world-readable, it's quite likely that I would be able to >>> control this URL on your user's machines: >> >> I notice that WebKitGTK+ disables this by default, good =). > > Awesome. :) > >> I think, though, that the AFS/NFS issue you mention is more general and >> shouldn't be a motivating factor. We have many GNU/Linux users not in >> corporate networks, these days, as well, and I think we should not be >> designing everything for big installations (those usually have admins >> who can worry about this kind of issue). >> >> Also, it looks like you can access windows shares using >> file://server/folder/file.html, so this doesn't seem to be UNIX-specific >> in any way. I also bet Mac can be made to use NFS, and AFS, so, again, I >> fail to see this as particularly important on non-Mac UNIX-likes. > > I'm not sure I quite followed your line of reasoning here. Are you > suggesting that everyone should use the more secure setting or are you > saying that you don't think this is an important security measure in > non-enterprise settings? > > I agree that everyone should disable universal access for file URLs. > In fact, I think we should make it the default because the current > default is pretty dangerous. > > Adam > > > ------------------------------ > > Message: 5 > Date: Mon, 24 Aug 2009 10:11:19 -0300 > From: Gustavo Noronha Silva <gns(a)gnome.org> > To: Adam Barth <abarth(a)webkit.org> > Cc: webkit-dev(a)lists.webkit.org > Subject: Re: [webkit-dev] Security advice for linux browsers based on > WebKit > Message-ID: <1251119479.6026.47.camel(a)goiaba.horta> > Content-Type: text/plain > > On Sun, 2009-08-23 at 21:30 -0700, Adam Barth wrote: >> > I think, though, that the AFS/NFS issue you mention is more general and >> > shouldn't be a motivating factor. We have many GNU/Linux users not in >> > corporate networks, these days, as well, and I think we should not be >> > designing everything for big installations (those usually have admins >> > who can worry about this kind of issue). >> > >> > Also, it looks like you can access windows shares using >> > file://server/folder/file.html, so this doesn't seem to be UNIX-specific >> > in any way. I also bet Mac can be made to use NFS, and AFS, so, again, I >> > fail to see this as particularly important on non-Mac UNIX-likes. >> >> I'm not sure I quite followed your line of reasoning here. Are you >> suggesting that everyone should use the more secure setting or are you >> saying that you don't think this is an important security measure in >> non-enterprise settings? > > I am saying that we should be careful not to design things with 'Linux > is mostly used in enterprise settings' in mind. There is no reason to > treat it differently than the other desktops; I myself have never used > NFS or AFS, nor have many people I know, even though I've been using > GNU/Linux for ~10 years now. And, as I pointed out, the same potential > problem with networked file systems may happen with Windows or Mac. > >> I agree that everyone should disable universal access for file URLs. >> In fact, I think we should make it the default because the current >> default is pretty dangerous. > > So, to clear up my position regarding the actual meat of the proposal: I > agree this is an important security concern. Doing that in libraries > right now will break API expectations, though, so I think if it is done, > this should be done first by documenting the intent to change, and then > changing after a reasonable amount of time. Of course browser > applications can do it right now, though =) > > See you, > > -- > Gustavo Noronha Silva <gns(a)gnome.org> > GNOME > > > > ------------------------------ > > _______________________________________________ > webkit-dev mailing list > webkit-dev(a)lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > End of webkit-dev Digest, Vol 51, Issue 26 > ****************************************** > -- Ravi Swami EnMedia Software Technologies

1 0