Re: [webkit-dev] Question on standards mode vs. site compatibility

[David Kilzer]

Both Firefox  and WebKit 
 allow you to file evangelism bugs on any web site.  
Perhaps it would be best to try that approach first?

Dave



>
>From: Chris Evans 
>To: Darin Adler 
>Cc: webkit-dev@lists.webkit.org
>Sent: Tue, November 10, 2009 8:59:39 PM
>Subject: Re: [webkit-dev] Question on standards mode vs. site compatibility
>
>>On Tue, Nov 10, 2009 at 8:37 PM, Darin Adler  wrote:
>
>On Nov 2, 2009, at 11:19 PM, Chris Evans wrote:
>>
>>Whilst mining a large list of URLs, I came across some sites that render 
>>incorrectly in WebKit but fine in IE.
>>>
>>>
>>>It turns out there exist some sites which declare themselves standards 
>>>complaint in their HTML via their DTD. These sites then proceed to try and 
>>>load CSS resources with the incorrect MIME type. This promptly fails due to 
>>>standards mode.
>>>
>>>
>>>e.g.
>>>http://web.pcc.gov.tw/ uses application/x-pointplus
>>>http://www.emart.co.kr/index.jsp uses application/css
>>>http://www.fotocolombo.it/shop/index.php uses text-css (note the hyphen in 
>>>place of a slash)
>>>application/octet stream also appears to be a favourite.
>>
>>
>>That's unfortunate. Out of curiosity, how do these sites behave in Firefox?
>
>
>Broken, in the same way. Fine in IE.
>
>
>
>>
>>What is "enforceCSSMIMETypeInStrictMode()"? Is it a global setting or is 
>>there some per-page metadata somewhere?
>>
>>It’s a setting for applications. For web browsers it is set to true. It is 
>>not per-page.
>>
>>
>>
>>
>>We can relax the MIME type list we enforce for "strict mode" without breaking 
>>ACID3, although I'm not even sure that's desirable? Is it worth me worrying 
>>about this at all or is the correct solution that these sites are just broken 
>>and need to fix themselves at some stage? (Pragmatically, I worry that these 
>>sites will never fix themselves so users of WebKit-based browsers are SOL).
>>
>>Sounds like a tough choice. It would be unfortunate to have to have a white 
>>list of sites that violate this rule.
>
>
>I agree we don't want to be listing sites.
>Our options would seem to be:
>- Do nothing
>- Permit application/x-point-plus and application/css as valid CSS MIME types. 
>This would fix some unknown number of sites, and retain ACID3 compatibility. 
>(ACID3 checks for CSS load failure with text/plain, I think).
>
>
>Cheers
>Chris
>
>
>
-- Darin
>>
>>
>___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Question on standards mode vs. site compatibility

[Chris Evans]

On Tue, Nov 10, 2009 at 8:37 PM, Darin Adler  wrote:

> On Nov 2, 2009, at 11:19 PM, Chris Evans wrote:
>
> Whilst mining a large list of URLs, I came across some sites that render
> incorrectly in WebKit but fine in IE.
>
> It turns out there exist some sites which declare themselves standards
> complaint in their HTML via their DTD. These sites then proceed to try and
> load CSS resources with the incorrect MIME type. This promptly fails due to
> standards mode.
>
> e.g.
> http://web.pcc.gov.tw/ uses application/x-pointplus
> http://www.emart.co.kr/index.jsp uses application/css
> http://www.fotocolombo.it/shop/index.php uses text-css (note the hyphen in
> place of a slash)
> application/octet stream also appears to be a favourite.
>
>
> That's unfortunate. Out of curiosity, how do these sites behave in Firefox?
>

Broken, in the same way. Fine in IE.


> What is "enforceCSSMIMETypeInStrictMode()"? Is it a global setting or is
> there some per-page metadata somewhere?
>
>
> It’s a setting for applications. For web browsers it is set to true. It is
> not per-page.
>
>
> We can relax the MIME type list we enforce for "strict mode" without
> breaking ACID3, although I'm not even sure that's desirable? Is it worth me
> worrying about this at all or is the correct solution that these sites are
> just broken and need to fix themselves at some stage? (Pragmatically, I
> worry that these sites will never fix themselves so users of WebKit-based
> browsers are SOL).
>
>
> Sounds like a tough choice. It would be unfortunate to have to have a white
> list of sites that violate this rule.
>

I agree we don't want to be listing sites.
Our options would seem to be:
- Do nothing
- Permit application/x-point-plus and application/css as valid CSS MIME
types. This would fix some unknown number of sites, and retain ACID3
compatibility. (ACID3 checks for CSS load failure with text/plain, I think).

Cheers
Chris


> -- Darin
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] WTFNoncopyable namespace and ADL

[Darin Adler]

On Nov 8, 2009, at 12:21 AM, Chris Jerdonek wrote:

> I have a question regarding JSC's WTFNoncopyable::Noncopyable class and 
> argument-dependent lookup (ADL).  It seems like an old decision may have been 
> unintentionally undone in changeset 46933.

I’m surprised that nothing depended on the argument-dependent lookup technique. 
We should see if we can demonstrate the the problem this causes.

> It seems like either the WTFNoncopyable namespace should be changed to WTF 
> and the comment removed, or else FastAllocBase should be put into its own 
> namespace as well (or something equivalent).

Yes, one of these should be done. But it’s not urgent.

-- Darin

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Question on standards mode vs. site compatibility

[Darin Adler]

On Nov 2, 2009, at 11:19 PM, Chris Evans wrote:

> Whilst mining a large list of URLs, I came across some sites that render 
> incorrectly in WebKit but fine in IE.
> 
> It turns out there exist some sites which declare themselves standards 
> complaint in their HTML via their DTD. These sites then proceed to try and 
> load CSS resources with the incorrect MIME type. This promptly fails due to 
> standards mode.
> 
> e.g.
> http://web.pcc.gov.tw/ uses application/x-pointplus
> http://www.emart.co.kr/index.jsp uses application/css
> http://www.fotocolombo.it/shop/index.php uses text-css (note the hyphen in 
> place of a slash)
> application/octet stream also appears to be a favourite.

That's unfortunate. Out of curiosity, how do these sites behave in Firefox?

> What is "enforceCSSMIMETypeInStrictMode()"? Is it a global setting or is 
> there some per-page metadata somewhere?

It’s a setting for applications. For web browsers it is set to true. It is not 
per-page.

> We can relax the MIME type list we enforce for "strict mode" without breaking 
> ACID3, although I'm not even sure that's desirable? Is it worth me worrying 
> about this at all or is the correct solution that these sites are just broken 
> and need to fix themselves at some stage? (Pragmatically, I worry that these 
> sites will never fix themselves so users of WebKit-based browsers are SOL).

Sounds like a tough choice. It would be unfortunate to have to have a white 
list of sites that violate this rule.

-- Darin

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] caching of static files

[Darin Adler]

On Nov 10, 2009, at 2:29 PM, Rick Gigger wrote:

> I have noticed that Safari and Firefox seem to use different strategies for 
> caching static files. It seems that when I have the expiration headers set 
> properly that Firefox does not request them at all until they are expired but 
> Safari requests them gut gets back 304 "not modified" responses. Is one of 
> those right or wrong? Does the http spec allow for either behavior?

The behavior you are talking about is called revalidation. The http 
specification specifies when revalidation should be done. For a particular test 
case you can read the HTTP 1.1 specification and figure out if the behavior is 
correct.

If the Safari behavior is incorrect, the bug could either be in the CFNetwork 
library or in WebKit. If the bug is in the CFNetwork library then it needs to 
be reported at  but if it is in WebKit, you could 
instead report it at . If you don’t know which it is OK 
to start with WebKit.

-- Darin

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] "using namespace" style guideline

[Darin Adler]

On Nov 10, 2009, at 7:41 PM, Chris Jerdonek wrote:

> Hi, I have a question about the last of the WebKit Coding Style Guidelines:
> 
> http://webkit.org/coding/coding-style.html
> 
> It's the second of these two:
> 
> 1. Any "using namespace" statements for a nested namespace whose parent 
> namespace is also defined in a file must be declared within that namespace 
> definition.
> 
> 2. Any other "using namespace" statements must be declared before the first 
> namespace definition in the file.

No "using namespace" statements are permitted in header files. The guidelines 
are talking about non-header files. We should clarify that.

-- Darin

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] "using namespace" style guideline

[Chris Jerdonek]

Hi, I have a question about the last of the WebKit Coding Style Guidelines:

http://webkit.org/coding/coding-style.html

It's the second of these two:

1. Any "using namespace" statements for a nested namespace whose
parent namespace is also defined in a file must be declared within
that namespace definition.

2. Any other "using namespace" statements must be declared before the
first namespace definition in the file.

Unlike most or all of the other rules, this one can affect
compilation.  So I was wondering what the rule is for.

For example, say I want to write the following in an existing header
file to avoid having to fully qualify several identifiers in the WTF
namespace:

namespace MyNewNameSpace {

using namespace WTF;

// code

}

Following rule 2 and putting the using statement outside the namespace
can cause compilation errors elsewhere in the project (due to
ambiguous overloads for bringing the WTF namespace into files already
including the above).  This actually happened to me while doing some
minor refactoring.

If I want to keep the "using namespace" statement, it seems like the
style guideline would require me to do an unknown amount of
refactoring outside the file.

Let me know your thoughts.

Thanks,
--Chris
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] caching of static files

[Rick Gigger]

Please let me know if this is not the right place to post this question.  I am 
new to this list.

I have noticed that Safari and Firefox seem to use different strategies for 
caching static files.  It seems that when I have the expiration headers set 
properly that Firefox does not request them at all until they are expired but 
Safari requests them gut gets back 304 "not modified" responses.  Is on of 
those right or wrong?  Does the http spec allow for either behavior?

Thanks,

Rick
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] ruby annotation layout tests

[Andras Becsi]

Hello, I have a question about the following HTML5 ruby annotation 
(http://www.w3.org/TR/ruby/) layout tests:


fast/ruby/ruby-empty-rt.html
fast/ruby/ruby-length.html
fast/ruby/ruby-run-break.html
fast/ruby/ruby-runs-spans.html
fast/ruby/ruby-runs.html
fast/ruby/ruby-simple-rp.html
fast/ruby/ruby-simple.html
fast/ruby/ruby-trailing.html
fast/ruby/rubyDOM-insert-rt.html
fast/ruby/rubyDOM-insert-text1.html
fast/ruby/rubyDOM-insert-text2.html
fast/ruby/rubyDOM-insert-text3.html
fast/ruby/rubyDOM-remove-rt1.html
fast/ruby/rubyDOM-remove-rt2.html
fast/ruby/rubyDOM-remove-text1.html
fast/ruby/rubyDOM-remove-text2.html

Is there an explicit need that the texts in these tests need to be 
japanese? Could they be changed to have english texts in them and add 
some tests that test if japanese fonts are supported correctly?


Thanks in advance!
Andras (bbandix)
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] WTFNoncopyable namespace and ADL

[Chris Jerdonek]

I have a question regarding JSC's WTFNoncopyable::Noncopyable class
and argument-dependent lookup (ADL).  It seems like an old decision
may have been unintentionally undone in changeset 46933 (first
attempted in 46877).

The Noncopyable class (currently JavaScriptCore/wtf/Noncopyable.h) was
originally added in Feb 2006 with the following comment:

// We don't want argument-dependent lookup to pull in everything
// from the KXMLCore [now WTF] namespace when you use Noncopyable,
// so put it in its own namespace.

namespace KXMLCoreNoncopyable {

class Noncopyable {

( 
http://trac.webkit.org/changeset/12523/trunk/JavaScriptCore/kxmlcore/Noncopyable.h
)

Then, in changeset 46933 (August 2009), the class declaration was changed to--

namespace WTFNoncopyable {

-class Noncopyable {
+class Noncopyable : public FastAllocBase {

( http://trac.webkit.org/changeset/46933/trunk/JavaScriptCore/wtf/Noncopyable.h
)

But FastAllocBase is in the WTF namespace, defeating the aim of the commenter.

It seems like either the WTFNoncopyable namespace should be changed to
WTF and the comment removed, or else FastAllocBase should be put into
its own namespace as well (or something equivalent).  I'm not sure how
important it is to preserve the original ADL behavior.

--Chris
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] access webkit-fake-url data

[Clifford Meece]

When an image (for example) is pasted from the clipboard into a webkit
editable content region, the source code looks like this:

webkit-fake-url://DCAC99B9-BA40-4BA7-A419-9C60AAB081DA/image.png

Where is the actual data stored in this instance?

-- 
View this message in context: 
http://old.nabble.com/access-webkit-fake-url-data-tp26200961p26200961.html
Sent from the Webkit mailing list archive at Nabble.com.

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] InkML

[Ishan Ahuja]

Hi,

I was wondering if there are any plans of implementing InkML (http://www.w3.org/2002/mmi/ink 
) rendering in webkit - or would you rather have it as a plug-in.


Thanks,
Ishan
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Running WebGL layout tests

[Kenneth Russell]

Hi,

Trying to run the WebGL layout tests in LayoutTests/fast/canvas/webgl.
Here's the command line I'm using:

run-webkit-tests --debug LayoutTests/fast/canvas/webgl/[test name.html]

(I built WebKit --debug.)

All of the tests fail while attempting to fetch the 3D context.
(TypeError: Result of expression 'context' [undefined] is not an
object.) The same tests run fine when run under "run-safari --debug".

Do I need to do some other "defaults write" or other setup to allow
the layout test harness to run with WebGL enabled?

Thanks,

-Ken
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Question on standards mode vs. site compatibility

[Chris Evans]

Hi,

Whilst mining a large list of URLs, I came across some sites that render
incorrectly in WebKit but fine in IE.

It turns out there exist some sites which declare themselves standards
complaint in their HTML via their DTD. These sites then proceed to try and
load CSS resources with the incorrect MIME type. This promptly fails due to
standards mode.

e.g.
http://web.pcc.gov.tw/ uses application/x-pointplus
http://www.emart.co.kr/index.jsp uses application/css
http://www.fotocolombo.it/shop/index.php uses text-css (note the hyphen in
place of a slash)
application/octet stream also appears to be a favourite.

I saw this code in HTMLLinkElement::setCSSStyleSheet

// Check to see if we should enforce the MIME type of the CSS resource
in strict mode.
// Running in iWeb 2 is one example of where we don't want to -

if (enforceMIMEType && document()->page() &&
!document()->page()->settings()->enforceCSSMIMETypeInStrictMode())
enforceMIMEType = false;

What is "enforceCSSMIMETypeInStrictMode()"? Is it a global setting or is
there some per-page metadata somewhere?

We can relax the MIME type list we enforce for "strict mode" without
breaking ACID3, although I'm not even sure that's desirable? Is it worth me
worrying about this at all or is the correct solution that these sites are
just broken and need to fix themselves at some stage? (Pragmatically, I
worry that these sites will never fix themselves so users of WebKit-based
browsers are SOL).


Cheers
Chris
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] access webkit-fake-url data?

[Clifford Meece]

When you paste image content into an editable content region, webkit  
produces URL's similar to the following:


webkit-fake-url://DCAC99B9-BA40-4BA7-A419-9C60AAB081DA/image.png

Is there anyway to access that data?  In particular I'm trying to get  
at the data from a tinyMCE instance running in safari 4.  My goal  
would be to programmatically scour the HTML input, look for the webkit- 
fake-url tags, access the original image, upload it to the destination  
blog, and then rewrite the image links.  I realize that their may be  
significant sandbox rules preventing me from doing this, but it would  
be nice to know where the original data is stored and any ways to  
access it.




Clifford Meece
Professional IT Services

T: (312) 607-5189
F: (773) 292-6372
E: clifford.me...@me.com
http://cliffordmeece.com


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] git.webkit.org/WebKit.git out of sync from svn repository?

[Mark Rowe]

On 2009-11-10, at 13:58, Yaar Schnitman wrote:

> Hi all,
> 
> I think we have this problem again. Webkit svn is on r50761, but I can only 
> git pull up to r50738.

This is fixed.

- Mark

> On Sun, Nov 8, 2009 at 5:11 PM, Fumitoshi Ukai (鵜飼文敏)  
> wrote:
> On Sat, Nov 7, 2009 at 6:10 AM, William Siegrist  wrote:
> On Nov 5, 2009, at 8:32 PM, Fumitoshi Ukai (鵜飼文敏) wrote:
> 
> > I think svn has r50586 (accodring to trac.webkit.org), but git only pulls 
> > r50565now.
> > Even I clone git repository from git://git.webkit.org/WebKit.git again, it 
> > only has r50565.
> > Is it out of sync?
> 
> 
> We had syncing issues yesterday, but they look fixed now. Can you retry?
> 
> It seems working now.
> Thanks!
> ukai
>  
> 
> -Bill
> 
> 
> 
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> 
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev



smime.p7s
Description: S/MIME cryptographic signature
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] git.webkit.org/WebKit.git out of sync from svn repository?

[Yaar Schnitman]

Hi all,

I think we have this problem again. Webkit svn is on r50761, but I can only
git pull up to r50738.

-Yaar

On Sun, Nov 8, 2009 at 5:11 PM, Fumitoshi Ukai (鵜飼文敏) wrote:

> On Sat, Nov 7, 2009 at 6:10 AM, William Siegrist wrote:
>
>> On Nov 5, 2009, at 8:32 PM, Fumitoshi Ukai (鵜飼文敏) wrote:
>>
>> > I think svn has r50586 (accodring to trac.webkit.org), but git only
>> pulls r50565now.
>> > Even I clone git repository from git://git.webkit.org/WebKit.git again,
>> it only has r50565.
>> > Is it out of sync?
>>
>>
>> We had syncing issues yesterday, but they look fixed now. Can you retry?
>>
>
> It seems working now.
> Thanks!
> ukai
>
>
>>
>> -Bill
>>
>>
>>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Layering weirdness in chrome tree

[Adam Barth]

That sounds like a bug to me.  Historically the chromium port hasn't
had a strong distinction between WebKit and WebCore/platform, but I
think it's a worthwhile distinction to make.

Adam


On Tue, Nov 10, 2009 at 11:53 AM, Oliver Hunt  wrote:
> I just noticed that there are a bunch of WebCore platform implementations
> being landed in Chrome's WebKit API rather than in WebCore/platform.  This
> seems incorrect to me as there is no other place where this sort of
> mis-layering occurred, the obvious files that stand out are:
>
> ApplicationCacheHost.cpp
> GraphicsContext3D.cpp
> MediaPlayerPrivateChromium.cpp
> PlatformMessagePortChannel.*
> ResoureHandle.cpp
> DOMUtilitiesPrivate.*
>
> I see no obvious reason for these being placed in WebKit -- as far as I can
> tell these represent a layering violation: it's not possible to build the
> WebCore directory into it's own library due to the hard dependency on the
> chrome webkit 'api'.
>
> --Oliver
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Layering weirdness in chrome tree

[Oliver Hunt]

I just noticed that there are a bunch of WebCore platform  
implementations being landed in Chrome's WebKit API rather than in  
WebCore/platform.  This seems incorrect to me as there is no other  
place where this sort of mis-layering occurred, the obvious files that  
stand out are:


ApplicationCacheHost.cpp
GraphicsContext3D.cpp
MediaPlayerPrivateChromium.cpp
PlatformMessagePortChannel.*
ResoureHandle.cpp
DOMUtilitiesPrivate.*

I see no obvious reason for these being placed in WebKit -- as far as  
I can tell these represent a layering violation: it's not possible to  
build the WebCore directory into it's own library due to the hard  
dependency on the chrome webkit 'api'.


--Oliver

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev