[webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Adam Barth
In July 2010, there was a thread on webkit-dev about removing support for the -khtml- and -apple- vendor prefixes: https://lists.webkit.org/pipermail/webkit-dev/2010-July/013519.html At the time, we tried an approach recommended by David Hyatt

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Ryosuke Niwa
On Thu, Apr 5, 2012 at 1:08 AM, Adam Barth wrote: > In July 2010, there was a thread on webkit-dev about removing support > for the -khtml- and -apple- vendor prefixes: > > https://lists.webkit.org/pipermail/webkit-dev/2010-July/013519.html > > At the time, we tried an approach recommended by Dav

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Allan Sandfeld Jensen
On Thursday 05 April 2012, Adam Barth wrote: > In July 2010, there was a thread on webkit-dev about removing support > for the -khtml- and -apple- vendor prefixes: > > https://lists.webkit.org/pipermail/webkit-dev/2010-July/013519.html > > At the time, we tried an approach recommended by David Hy

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Alexey Proskuryakov
05.04.2012, в 01:08, Adam Barth написал(а): > Based on this information, I've posted a patch that limits the -apple- > and -khtml- vendor prefixes to ENABLE(DASHBOARD_SUPPORT): > > https://bugs.webkit.org/show_bug.cgi?id=83256 > > This approach lets ports that wish to remain compatible with Das

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Benjamin Poulain
On Thu, Apr 5, 2012 at 1:08 AM, Adam Barth wrote: > In July 2010, there was a thread on webkit-dev about removing support > for the -khtml- and -apple- vendor prefixes: As a first step toward deprecation, it would be nice if browsers could issue a warning in the console when such property prefix

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Adam Barth
One option is to start evaluating the compat implications by disabling the prefixes in Chrome. If we have a positive experience we can disable them in more ports/configurations over time, hopefully arriving where you suggest while avoiding the stress of release blocking bugs. Adam On Apr 5, 2012

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Adam Barth
One option is to start evaluating the compat implications by disabling the prefixes in Chrome. If we have a positive experience we can disable them in more ports/configurations over time, hopefully arriving where you suggest while avoiding the stress of rel On Apr 5, 2012 10:14 AM, "Alexey Proskur

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012-04-05 Thread Adam Barth
(Previous email got cut off) ...release blocking bugs. On Apr 5, 2012 2:25 PM, "Adam Barth" wrote: > One option is to start evaluating the compat implications by disabling the > prefixes in Chrome. If we have a positive experience we can disable them > in more ports/configurations over time, ho

Re: [webkit-dev] Is anyone not using PREEMPT_GEOLOCATION_PERMISSION?

2012-04-05 Thread Benjamin Poulain
On Thu, Mar 29, 2012 at 3:00 PM, Benjamin Poulain wrote: > I could not find any case where PREEMPT_GEOLOCATION_PERMISSION is not > used. Unless someone does not use this flag, I plan to remove the flag > and the related useless code. I did not get any answer for a week. Here is the patch to clean

Re: [webkit-dev] Is anyone not using PREEMPT_GEOLOCATION_PERMISSION?

2012-04-05 Thread Ryosuke Niwa
On Thu, Apr 5, 2012 at 4:35 PM, Benjamin Poulain wrote: > On Thu, Mar 29, 2012 at 3:00 PM, Benjamin Poulain > wrote: > > I could not find any case where PREEMPT_GEOLOCATION_PERMISSION is not > > used. Unless someone does not use this flag, I plan to remove the flag > > and the related useless cod

Re: [webkit-dev] Is anyone not using PREEMPT_GEOLOCATION_PERMISSION?

2012-04-05 Thread Jeff Rogers
The BlackBerry port doesn't use that flag, we are fine with removing it. On Thu, Apr 5, 2012 at 8:34 PM, Ryosuke Niwa wrote: > On Thu, Apr 5, 2012 at 4:35 PM, Benjamin Poulain wrote: > >> On Thu, Mar 29, 2012 at 3:00 PM, Benjamin Poulain >> wrote: >> > I could not find any case where PREEMPT_GE

Re: [webkit-dev] Is anyone not using PREEMPT_GEOLOCATION_PERMISSION?

2012-04-05 Thread Ryosuke Niwa
Okay, thanks for the clarification. Given that the blackberry was the only port that listed this flag in the list of features, I think it's okay to remove this flag. As I mentioned earlier, the flag is pretty self-contained, so if this removal causes any inconvenience, we can always revert it late