Per http://www.webkit.org/coding/adding-features.html
I'm working on adding image-resolution support to WebKit.
http://www.w3.org/TR/2012/CR-css3-images-20120417/#image-resolution
The css3-images module is at candidate recommendation.
Folks interested can follow along:
Dave Hyatt is interested in doing more Paged Media stuff.
Any work in this area should be preceded by a conversation with Dave.
Simon
On Apr 27, 2012, at 11:47 AM, Eric Seidel wrote:
Ref-tests did not exist in WebKit when I last looked at this. I added
pdf printing tests, only to realize
Work is complete, fully working. Passing all the tests I could come up with:
https://github.com/eseidel/webkit/compare/master...seamless
I'm uploading and landing patches once reviewed again in bugzilla.
I do not plan to add an ENABLE, as this work is complete and will all
be landed by end of
On May 1, 2012, at 12:20 PM, Eric Seidel e...@webkit.org wrote:
Work is complete, fully working. Passing all the tests I could come up with:
https://github.com/eseidel/webkit/compare/master...seamless
I'm uploading and landing patches once reviewed again in bugzilla.
I do not plan to
On Tue, May 1, 2012 at 2:06 PM, Maciej Stachowiak m...@apple.com wrote:
On May 1, 2012, at 12:20 PM, Eric Seidel e...@webkit.org wrote:
Work is complete, fully working. Passing all the tests I could come up
with:
https://github.com/eseidel/webkit/compare/master...seamless
I'm
Is your goal to be able to disable the feature to prevent a late-known
security issue?
Or is your goal to universally disable seamless for a port entirely?
On Tue, May 1, 2012 at 2:06 PM, Maciej Stachowiak m...@apple.com wrote:
On May 1, 2012, at 12:20 PM, Eric Seidel e...@webkit.org wrote:
On May 1, 2012, at 3:31 PM, Eric Seidel e...@webkit.org wrote:
Is your goal to be able to disable the feature to prevent a late-known
security issue?
Or is your goal to universally disable seamless for a port entirely?
I'm not sure I understand the difference between these. The capability
On Tue, May 1, 2012 at 3:50 PM, Maciej Stachowiak m...@apple.com wrote:
On May 1, 2012, at 3:31 PM, Eric Seidel e...@webkit.org wrote:
Is your goal to be able to disable the feature to prevent a late-known
security issue?
Or is your goal to universally disable seamless for a port entirely?
On May 1, 2012, at 4:04 PM, Adam Barth aba...@webkit.org wrote:
On Tue, May 1, 2012 at 3:50 PM, Maciej Stachowiak m...@apple.com wrote:
On May 1, 2012, at 3:31 PM, Eric Seidel e...@webkit.org wrote:
Is your goal to be able to disable the feature to prevent a late-known
security issue?
Or
On Sun, Apr 29, 2012 at 7:33 PM, Maciej Stachowiak m...@apple.com wrote:
In the longer term, here's a few things we should think about:
- Historically, we've almost never removed prefixed versions of features that
get promoted to unprefixed. The marginal maintenance cost is low and there's
10 matches
Mail list logo