Hi there,
On Tue, Apr 24, 2012 at 11:48 PM, Edward O'Connor eocon...@apple.com wrote:
Eric Seidel wrote:
Assuming I'm understanding Kalle correctly, it seems this could
already be accomplished with @media resolution?
http://www.w3.org/TR/css3-mediaqueries/#resolution
@media screen and
Mozilla Firefox supports dynamic adding of resources into the
application cache for offline use with the function:
window.applicationCache.mozAdd(URI String)
https://developer.mozilla.org/en/nsIDOMOfflineResourceList
This is great for persistent storage of assets via javascipt. Instead
of
On Wed, Apr 25, 2012 at 3:22 AM, Kenneth Rohde Christiansen
kenneth.christian...@gmail.com wrote:
So the original iPhone has a dpi of 163, but it reported a CSS dpi of
96? meaning that in screen width it had around 3,3 CSS inches where as
the physical inches are more close to 1.96.
Why is
Hi WebKittens,
following the talk about Deprecating (web-facing) features and vendor
prefixing [1], we decided to create a guideline covering new
deprecations or un-prefixing [2]. The rationale is that this will
avoid a lot of the mistakes that we have made in the previous
deprecations and that
Assuming I'm understanding Kalle correctly, it seems this could
already be accomplished with @media resolution?
http://www.w3.org/TR/css3-mediaqueries/#resolution
Not to be too cute about it, but CSS dpi is _always_ 96 CSS pixels per CSS
inch. What this means onscreen is (almost) completely
Thanks Chris,
I'll go bring it up on the relevant w3.org lists (I'm guessing I'll start on
public-HTML-comments) and see where that takes me, after refining my idea a bit
to use more conventional naming, and to hopefully account for other scales than
2x in an elegant manner.
I just wanted to
Are you an expert on FOO?
Does your port need to know if BAR changes?
Are you sick and tired of those insert company name here people
breaking your favorite BAZ!?!?
Add yourself to the watchlist:
http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/common/config/watchlist
Especially if
As explained here:
http://trac.webkit.org/wiki/WatchList
The style-bot applies the watchlist regexps when it checks a patch,
and will CC you at that time.
On Wed, Apr 25, 2012 at 11:26 AM, Eric Seidel e...@webkit.org wrote:
Are you an expert on FOO?
Does your port need to know if BAR changes?
Hi everyone,
A while back, Apple's WebKit teams instituted a bot watching rotation to try to
get the bots for our ports to get and stay green. We've managed to consistently
stay around low single digits of failures, but the green doesn't seem to stick.
We think some folks in the community may
On Wednesday 25 April 2012, Chris Hutten-Czapski wrote:
Assuming I'm understanding Kalle correctly, it seems this could
already be accomplished with @media resolution?
http://www.w3.org/TR/css3-mediaqueries/#resolution
Not to be too cute about it, but CSS dpi is _always_ 96 CSS pixels
On Mon, Apr 23, 2012 at 4:13 PM, Jacob Goldstein jac...@adobe.com wrote:
At the recent WebKit Contributors Meeting, a process was drafted for
importing third party tests into WebKit.
I created a wiki page that captures the process that we came up with here:
Hi-
This has been on my mind lately too, so I'm happy that you brought it
up. I have a couple of questions:
Would it be possible to make mac's ews warn about test failures in the
same way that chromium-ews does? That's been super helpful for keeping
Chromium green.
Also, when you say pay
On Wed, Apr 25, 2012 at 2:34 PM, Adrienne Walker e...@google.com wrote:
Also, when you say pay attention, what level of involvement should
we expect for one committer making the bots go red on a port that they
are not primarily working on? Should we expect test expectation
rebaselining? Patch
On Wed, Apr 25, 2012 at 2:40 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Wed, Apr 25, 2012 at 2:34 PM, Adrienne Walker e...@google.com wrote:
Also, when you say pay attention, what level of involvement should
we expect for one committer making the bots go red on a port that they
are not
On Wed, Apr 25, 2012 at 2:51 PM, Dirk Pranke dpra...@chromium.org wrote:
Given that some people often land changes that break baselines on
every bot, and that we clearly don't expect the patch submitter to fix
every bot in this situation, how do you square that with what you just
wrote?
Good to know. I had stopped paying attention to many of the Apple bots for
the reason you mention.
It would be really helpful if someone could make the webkit-patch tooling
works correctly for the non-Chromium bots. Specifically, webkit-patch
rebaseline-test and webkit-patch garden-o-matic. They
On Wed, Apr 25, 2012 at 3:50 PM, Ojan Vafai o...@chromium.org wrote:
Good to know. I had stopped paying attention to many of the Apple bots for
the reason you mention.
It would be really helpful if someone could make the webkit-patch tooling
works correctly for the non-Chromium bots.
17 matches
Mail list logo
