Hey there,
I'd like to know what part of the CSS3 paged media module is currently
implemented in WebKit.
I see that the parser can handle most of it, yet at least margin boxes need
some work.
But when it comes to actually handling these properties - has there been any
work on this yet? There
Hey all,
I would like to work on the CSS3 Paged Media support, esp. the margin boxes.
I'm studying the code for some time now and would welcome it if someone could
assist me in figuring out what needs to be done...
First up, I think I should tackle the missing support in the parser, i.e.
On Friday 27 April 2012 10:08:13 Eric Seidel wrote:
When I last looked at the page media stuff (long ago). The problem
was mostly going to be testing. We don't have a good way to do
printing tests right now in WebKit.
Someone in the webkit community introduced me to the idea of reftests,
Ref-tests did not exist in WebKit when I last looked at this. I added
pdf printing tests, only to realize that pdfs include user/machine
information and thus are useless for x-machine testing.
If our ref-test mechanism works for large pages that could work well.
:) With printing tests you'll
OK, I've re-worked my proposal a bit from the feedback I've received,
and I'll submit to w3.org public-html-comments. Here's my revised
proposal:
Seeking feedback for my (hopefully relatively painless in practice
compared to the alternatives - i.e. -webkit-image-set and html5
image)
Hi Julien,
Thanks for the writeup! I definitely wanted to be in that discussion
but it conflicted with another discussion I wanted to be in. It looks
like I more or less agree with the writeup, though :).
That said, what sort of officialness does this
writeup/guideline/policy have? Do all the
On Fri, Apr 27, 2012 at 2:18 PM, Dirk Pranke dpra...@chromium.org wrote:
That said, what sort of officialness does this
writeup/guideline/policy have? Do all the ports agree that this is
what our stance should be?
Everyone seemed to agree we just need to discuss each deprecation on
webkit-dev
Is the concern that we've been deprecating too many things too quickly?
On Fri, Apr 27, 2012 at 5:00 PM, Benjamin Poulain benja...@webkit.org wrote:
On Fri, Apr 27, 2012 at 2:18 PM, Dirk Pranke dpra...@chromium.org wrote:
That said, what sort of officialness does this
writeup/guideline/policy
On Fri, Apr 27, 2012 at 5:10 PM, Eric Seidel e...@webkit.org wrote:
Is the concern that we've been deprecating too many things too quickly?
Quite the contrary. People were concerned about the way to deprecate
more stuff and making fewer mistakes when adding and removing features
:)
I think the concern is that, due to lack of clear standards, we end up not
knowing when we can remove things. Thus, we end up with a lot of inconclusive
and frustrating conversations, and people may shy away from even trying to
remove things.
BTW, the page at
Not having been to the meeting (but having read
https://trac.webkit.org/wiki/DeprecatingFeatures), it struck me as
though we were trying to add process (like we did for adding features
last year), to deter deprecating things.
On Fri, Apr 27, 2012 at 5:14 PM, Benjamin Poulain benja...@webkit.org
On Fri, Apr 27, 2012 at 5:17 PM, Maciej Stachowiak m...@apple.com wrote:
I think the concern is that, due to lack of clear standards, we end up not
knowing when we can remove things. Thus, we end up with a lot of inconclusive
and frustrating conversations, and people may shy away from even
12 matches
Mail list logo
