Done: https://bugs.webkit.org/show_bug.cgi?id=61096
On Wed, May 18, 2011 at 9:36 AM, Simon Fraser wrote:
> The best way to move forward would be to file a bug requesting that the
> prefixes be removed.
>
> Simon
>
>
> On May 18, 2011, at 9:31 AM, Brady Duga wrote:
>
> Though, in this case, the sp
The best way to move forward would be to file a bug requesting that the
prefixes be removed.
Simon
On May 18, 2011, at 9:31 AM, Brady Duga wrote:
> Though, in this case, the spec is at CR and has been since 2009. Is there an
> additional process to removing the vendor prefixes for WebKit? So,
Though, in this case, the spec is at CR and has been since 2009. Is there an
additional process to removing the vendor prefixes for WebKit? So, are they
still there because no one bothered to remove them, or because the consensus
is they should remain for some reason?
--Brady
On Wed, May 18, 2011
On May 18, 2011, at 6:36 AM, Sabri Aurrelia wrote:
> Why does webkit not provide support for native CSS3 attributes in its parsing
> engine where those attributes clearly coincide with most other browsers'
> attributes -and- the Candidate Recommendations set forth by W3?
>
> Let me put it this
Why does webkit not provide support for native CSS3 attributes in its
parsing engine where those attributes clearly coincide with most other
browsers' attributes -and- the Candidate Recommendations set forth by W3?
Let me put it this way: What is the purpose of every browser having
their own
5 matches
Mail list logo
