On Sat, Feb 16, 2013 at 11:26 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 10:50 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 16, 2013, at 10:16 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 6:54 PM, Adam Barth aba...@webkit.org wrote:
It's much easier
On Feb 17, 2013, at 12:08 AM, Adam Barth aba...@webkit.org wrote:
On Sat, Feb 16, 2013 at 11:26 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 10:50 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 16, 2013, at 10:16 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16,
On Feb 17, 2013, at 1:04 AM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 17, 2013, at 12:08 AM, Adam Barth aba...@webkit.org wrote:
On Sat, Feb 16, 2013 at 11:26 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 10:50 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 16,
On Feb 17, 2013, at 1:09 AM, Filip Pizlo fpi...@apple.com wrote:
On Feb 17, 2013, at 1:04 AM, Dirk Schulze dschu...@adobe.com wrote:
The discussion on each single feature let us forget the greater scope of
this problem. That is why I did not start with a concrete example.
What about
On Feb 17, 2013, at 1:28 AM, Maciej Stachowiak m...@apple.com wrote:
On Feb 17, 2013, at 1:09 AM, Filip Pizlo fpi...@apple.com wrote:
On Feb 17, 2013, at 1:04 AM, Dirk Schulze dschu...@adobe.com wrote:
The discussion on each single feature let us forget the greater scope of
this
On Sun, Feb 17, 2013 at 7:26 AM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 17, 2013, at 1:28 AM, Maciej Stachowiak m...@apple.com wrote:
On Feb 17, 2013, at 1:09 AM, Filip Pizlo fpi...@apple.com wrote:
On Feb 17, 2013, at 1:04 AM, Dirk Schulze dschu...@adobe.com wrote:
The discussion on
On Sun, Feb 17, 2013 at 7:26 AM, Dirk Schulze dschu...@adobe.com wrote:
Then we should face it. Prefixed content for CSS gradients, animation,
transition, transforms, CSS Image functions, masking and a lot more will
not go away. This basically means we will need to support them for an
On Feb 17, 2013, at 2:47 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Feb 17, 2013 at 7:26 AM, Dirk Schulze dschu...@adobe.com wrote:
Then we should face it. Prefixed content for CSS gradients, animation,
transition, transforms, CSS Image functions, masking and a lot more will not
go
On Feb 17, 2013, at 3:02 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 17, 2013, at 9:16 AM, Adam Barth aba...@webkit.org wrote:
On Sun, Feb 17, 2013 at 7:26 AM, Dirk Schulze dschu...@adobe.com wrote:
Then we should face it. Prefixed content for CSS gradients, animation,
Hi,
There are several steps on deprecating features[1]. My question is about
deprecating a whole interface and throwing warnings that the feature is
deprecated.
If I have the following interface for deprecation:
[Constructor]
interface Bla {
attribute bar;
void foo();
}
It's much easier to discuss a concrete example. Which interface are
you interested in deprecating?
Adam
On Sat, Feb 16, 2013 at 5:28 PM, Dirk Schulze dschu...@adobe.com wrote:
Hi,
There are several steps on deprecating features[1]. My question is about
deprecating a whole interface and
On Feb 16, 2013, at 6:54 PM, Adam Barth aba...@webkit.org wrote:
It's much easier to discuss a concrete example. Which interface are
you interested in deprecating?
I can understand that it is easier to discuss on a concrete example, even if I
would like to discuss this in a general scope.
On Feb 16, 2013, at 10:16 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 6:54 PM, Adam Barth aba...@webkit.org wrote:
It's much easier to discuss a concrete example. Which interface are
you interested in deprecating?
I can understand that it is easier to discuss on a
On Feb 16, 2013, at 10:50 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 16, 2013, at 10:16 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 6:54 PM, Adam Barth aba...@webkit.org wrote:
It's much easier to discuss a concrete example. Which interface are
you
14 matches
Mail list logo
