On rendering an application of size 1280X720 using webkit which is to be
finally shown on 960X540 window, after resizing the page using
WKPageSetZoomfactor API, layout of a div element breaks( made from three
images).Is their anyway to avoid that by using some other API or Is it
possible that may
This plan sounds reasonable to me. No disruption of Chrome extensions in the
short term, but we would better align with each other and with standards in the
longer term.
Jon?
Regards,
Maciej
On Feb 9, 2012, at 2:48 PM, Aaron Boodman wrote:
On Wed, Feb 8, 2012 at 7:50 PM, Maciej Stachowiak
On Feb 10, 2012, at 4:09 PM, Ryosuke Niwa wrote:
Hi all,
In general, the decision of whether a given feature is enabled or not is made
by each port. However, at last year's W3C TPAC, there were complaints from
other participants about WebKit shipping half-baked implementations and
On Feb 10, 2012, at 4:20 PM, Dirk Pranke wrote:
I think at one point Adam indicated he wanted to use them for the
Apple Win port, but he is still using the Skipped files since the Win
port is still using ORWT on the bots.
That said, I understand why you're asking this (I think), but I
On Mon, Feb 13, 2012 at 1:02 PM, Maciej Stachowiak m...@apple.com wrote:
I think you raise a good point. Another point worth mentioning is that
sometimes a feature can be complete and useful in one port, but half-baked
in another (for example, fullscreen API was shipped in Safari and at the
On Mon, Feb 13, 2012 at 1:06 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 10, 2012, at 4:20 PM, Dirk Pranke wrote:
I think at one point Adam indicated he wanted to use them for the
Apple Win port, but he is still using the Skipped files since the Win
port is still using ORWT on the
It's hard for me to advice you on how to optimize your website but will you
be interested in creating a reduced test cases where WebKit is slow?
I'm sure we can (at least try to) resolve your pain points if you can
create benchmarks licensed under BSD/LGPL or WebKit performance tests (see
Hi Steve.
Do you have a test account with a fixed content set that we can use for
profiling?
It's hard to speculate about performance issues without profiling, and we might
get confused if we all profile different content.
Thanks,
Geoff
___
Profiling scrolling through my own timeline, and focusing on points where the
CPU hit 100% or greater, I saw this:
(1) 50% of time spent in style calculation forced by accessing
element.offsetHeight in JavaScript.
We then have JS which checks the heights of all the
stories on in the
On Mon, Feb 13, 2012 at 1:02 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 10, 2012, at 4:09 PM, Ryosuke Niwa wrote:
Hi all,
In general, the decision of whether a given feature is enabled or not is
made by each port. However, at last year's W3C TPAC, there were complaints
from other
Related to this is the question of what ports are even on for various ports.
I don't believe it's possible today to list what features are on for
what ports. At least not without a lot of emailing...
Before designing a finer-granularity on/off switch, it seems it might
make sense to have a
On Feb 13, 2012, at 1:40 PM, Ojan Vafai wrote:
On Mon, Feb 13, 2012 at 1:06 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 10, 2012, at 4:20 PM, Dirk Pranke wrote:
For example, we might want to use only Skipped files for tests that
are always planned to be skipped, and
On Feb 13, 2012, at 1:21 PM, Ryosuke Niwa wrote:
On Mon, Feb 13, 2012 at 1:02 PM, Maciej Stachowiak m...@apple.com wrote:
I think you raise a good point. Another point worth mentioning is that
sometimes a feature can be complete and useful in one port, but half-baked in
another (for
On Mon, Feb 13, 2012 at 3:09 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 13, 2012, at 1:40 PM, Ojan Vafai wrote:
On Mon, Feb 13, 2012 at 1:06 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 10, 2012, at 4:20 PM, Dirk Pranke wrote:
For example, we might want to use only
I’m really enjoying how the cleanup is going so far. The IDL attribute names
are noticeably clearer and more consistent.
-- Darin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
(Re-sending from the right address...)
I'd +1 Adam's point.
It would be great if we can do something like webkit-build --gtk
--stable, webkit-build --chromium --canary or webkit-build
--nightly where the script read the central configuration file and
find an appropriate configuration. In this
Not sure what tools you have used but you may find this helpful:
http://code.google.com/webtoolkit/speedtracer/
On Sat, Feb 11, 2012 at 10:02 PM, Steven Young styoung.bi...@gmail.comwrote:
[cross posting from mozilla's dev lists]
I'm on the Timeline team at Facebook, which is going to be the
Hi! Lots of responses below (mashed previous replies together for topic
coherency):
John Gregg wrote:
Which missing aspects of the Feature permissions spec are you concerned about?
I was only referring to the fact that the spec calls for a separate generic
interface for permissions with a
On Mon, Feb 13, 2012 at 5:23 PM, Jon Lee jon...@apple.com wrote:
I also have concerns about backwards compatibility support. Aside from
Gmail, what other web sites have integrated the notifications feature? I
could only find example pages, one of which was using already an outdated
API.
On Mon, Feb 13, 2012 at 5:29 PM, Adam Barth aba...@webkit.org wrote:
On Mon, Feb 13, 2012 at 5:23 PM, Jon Lee jon...@apple.com wrote:
I also have concerns about backwards compatibility support. Aside from
Gmail, what other web sites have integrated the notifications feature? I
could only
On Mon, Feb 13, 2012 at 5:23 PM, Jon Lee jon...@apple.com wrote:
Hi! Lots of responses below (mashed previous replies together for topic
coherency):
John Gregg wrote:
Which missing aspects of the Feature permissions spec are you concerned
about?
I was only referring to the fact that the
On Mon, Feb 13, 2012 at 5:31 PM, David Levin le...@chromium.org wrote:
On Mon, Feb 13, 2012 at 5:29 PM, Adam Barth aba...@webkit.org wrote:
On Mon, Feb 13, 2012 at 5:23 PM, Jon Lee jon...@apple.com wrote:
I also have concerns about backwards compatibility support. Aside from
Gmail, what
I think we're talking about a couple of different things now:
1) Table of what the WebKit community as a whole (instead of individual point
maintainers) thinks should be enabled in stable releases. This would be input
to port maintainers looking to make a release.
2) Documenting what enable
will you be interested in creating a reduced test cases where WebKit is slow?
Ryosuke - For now, user complaints about slowness are too
unpredictable and poorly defined for me to create a simple test case.
I will report back here if we reach that point.
(1) 50% of time spent in style
On Tue, Feb 14, 2012 at 11:09 AM, Maciej Stachowiak m...@apple.com wrote:
I think we're talking about a couple of different things now:
1) Table of what the WebKit community as a whole (instead of individual point
maintainers) thinks should be enabled in stable releases. This would be input
(1) 50% of time spent in style calculation forced by accessing
element.offsetHeight in JavaScript.
Geoff - I am going to bite the bullet and rip this logic out. We are
pushing too much complexity into the browser.
Bear in mind that I didn't do enough analysis to explain why the
26 matches
Mail list logo
