[webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Peter Beverloo
Good day, While going through WebCore for some CSS research I'm currently doing, I came across a piece of code[1] which translates all -khtml- and -apple- vendor-prefixes to -webkit-. This effectively means -apple-transform and -khtml-transform can both be used instead of -webkit-transform. I am

[webkit-dev] Remove me from your mailing list..

2010-07-12 Thread Johnson, Christopher
Please remove me from your mailing list. Thanks. V/R, Christopher Johnson | SAIC Electronic Technician 1 | Defense Solutions Group Office: 843-218-3064 | Fax 843-218-7727 Cell: 843-532-4285 | NIPR: christopher.john...@saic.com Science Applications International Corporation 1545

Re: [webkit-dev] Remove me from your mailing list..

2010-07-12 Thread Jeremy Orlow
Seriously? It's the first result: http://www.lmgtfy.com/?q=webkit-dev Clearly you overly value your own time if you couldn't even do a quick search on how to properly unsubscribe and instead spammed an entire mailing list. J On Mon, Jul 12, 2010 at 11:23 AM, Johnson, Christopher

[webkit-dev] Exposing FileReader to a worker

2010-07-12 Thread David Sanders
Hi all, I'm trying to expose the FileReader class to workers but am having a bit of trouble doing so. Initially I've tried to simply add FileReaderConstructor to WorkerContext.idl but still could not create a file reader from a worker. Afterwards, I read through the source and saw that the

Re: [webkit-dev] Exposing FileReader to a worker

2010-07-12 Thread David Sanders
Sorry I forgot to ask whether anyone knew what was required to add a class to a worker context. ;) David ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Eric Seidel
Sounds like an easy patch to post. I'm in favor of removing this support. Reducing the number of non-standard CSS properties we support seems like a good thing. -eric On Mon, Jul 12, 2010 at 1:53 AM, Peter Beverloo pe...@lvp-media.com wrote: Good day, While going through WebCore for some

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Eric Seidel
Please post a patch: http://webkit.org/coding/contributing.html On Mon, Jul 12, 2010 at 8:25 AM, Eric Seidel e...@webkit.org wrote: Sounds like an easy patch to post.  I'm in favor of removing this support.  Reducing the number of non-standard CSS properties we support seems like a good thing.

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Peter Beverloo
On Mon, Jul 12, 2010 at 18:00, Ryosuke Niwa rn...@webkit.org wrote: While converting all -khtml- properties to -webkit- may not be appropriate because there could be incompatible implementation of certain property, there are properties starting with -khtml- that are supposed to be supported

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Ryosuke Niwa
On Mon, Jul 12, 2010 at 9:20 AM, Peter Beverloo pe...@lvp-media.com wrote: I decided to take this issue to the mailing lists before posting a patch for such reasons. The Apple documentation which is referred to[1] in that bug has been updated to use WebKit's own vendor prefix, so I suspect

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Maciej Stachowiak
The reason for these is historical. Originally, we didn't use a separate vendor prefix for WebKit, just -khtml. Later we changed to -apple. Eventually we realized WebKit would not be an Apple-specific project forever, so we switched to -webkit. The main risk to removing the old prefixes is

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Peter Beverloo
Right now WebKit has by far the most prefixed elements[1], a significant part of which have not been standardized/drafted yet. Keeping the translation for all properties active practically triples the amount of supported vendor-specific CSS extensions, which cannot be desirable. I'm not opposed

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Peter Beverloo
Excuse me, I forgot to note the new bug + patch in my previous mail, although it was listed in the references. https://bugs.webkit.org/show_bug.cgi?id=42093 Regards, Peter Beverloo http://peter.sh/ On Mon, Jul 12, 2010 at 17:26, Eric Seidel e...@webkit.org wrote: Please post a patch:

Re: [webkit-dev] Bugzilla Question - Master Bug vs Component?

2010-07-12 Thread Beth Dakin
On Jul 10, 2010, at 1:17 AM, Alex Milowski wrote: I would think we'd close it when we've actually completely implemented MathML. If this is what you want the bug to represent, then it does make sense to keep all feature-implementation bugs related to this master bug, but none of the bug

Re: [webkit-dev] Bugzilla Question - Master Bug vs Component?

2010-07-12 Thread Sausset François
Le 12 juil. 2010 à 21:01, Beth Dakin a écrit : On Jul 10, 2010, at 1:17 AM, Alex Milowski wrote: I would think we'd close it when we've actually completely implemented MathML. If this is what you want the bug to represent, then it does make sense to keep all feature-implementation

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Maciej Stachowiak
On Jul 12, 2010, at 10:44 AM, Peter Beverloo wrote: Right now WebKit has by far the most prefixed elements[1], a significant part of which have not been standardized/drafted yet. Keeping the translation for all properties active practically triples the amount of supported vendor-specific CSS

Re: [webkit-dev] Bugzilla Question - Master Bug vs Component?

2010-07-12 Thread Maciej Stachowiak
On Jul 12, 2010, at 11:01 AM, Beth Dakin wrote: On Jul 10, 2010, at 1:17 AM, Alex Milowski wrote: I would think we'd close it when we've actually completely implemented MathML. If this is what you want the bug to represent, then it does make sense to keep all feature-implementation

Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread David Hyatt
On Jul 12, 2010, at 12:09 PM, Maciej Stachowiak wrote: The reason for these is historical. Originally, we didn't use a separate vendor prefix for WebKit, just -khtml. Later we changed to -apple. That's not quite right. Originally we just had -khtml- for CSS extensions, and then we used

[webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes

2010-07-12 Thread Peter Beverloo
Good day, While going through WebCore for some CSS research I'm currently doing, I came across a piece of code[1] which translates all -khtml- and -apple- vendor-prefixes to -webkit-. This effectively means -apple-transform and -khtml-transform can both be used instead of -webkit-transform. I am

Re: [webkit-dev] HTML5 MathML3 entities

2010-07-12 Thread Mike Marchywka
From: aba...@webkit.org Date: Sun, 11 Jul 2010 16:33:57 -0700 To: m...@apple.com CC: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] HTML5 MathML3 entities On Sat, Jul 10, 2010 at 6:28 PM, Maciej Stachowiak wrote: On Jul 10,

Re: [webkit-dev] Bugzilla Question - Master Bug vs Component?

2010-07-12 Thread Alex Milowski
On Mon, Jul 12, 2010 at 7:49 PM, Maciej Stachowiak m...@apple.com wrote: I think it's fine to enable MathML soon, as long as we make sure of the following: 1) Using a MathML-enabled build shouldn't cause stability problems or functional or performance regressions when browsing ordinary

Re: [webkit-dev] Bugzilla Question - Master Bug vs Component?

2010-07-12 Thread Maciej Stachowiak
On Jul 12, 2010, at 4:06 PM, Alex Milowski wrote: On Mon, Jul 12, 2010 at 7:49 PM, Maciej Stachowiak m...@apple.com wrote: I think it's fine to enable MathML soon, as long as we make sure of the following: 1) Using a MathML-enabled build shouldn't cause stability problems or