On Oct 7, 2013, at 11:55 PM, Chris Fleizach cfleiz...@apple.com wrote:
Hi Dirk,
On Oct 7, 2013, at 12:36 AM, Dirk Schulze dschu...@adobe.com wrote:
I am all for accessibility! But isn't the idea to keep content out of CSS so
that it does not interfere with accessibility as much as
On Oct 8, 2013, at 1:02 AM, Dirk Schulze dschu...@adobe.com wrote:
I hope you understand that I am not particularly concerned about Apples
screen reader solution. It is one implementation. I would like to know if
JAWS, NVDA, Dolphin and other are aboard.
Withe the exception of NVDA, the
I am all for accessibility! But isn't the idea to keep content out of CSS so
that it does not interfere with accessibility as much as possible?
The main problem with the 'content' property is that it is not accessible. Why
I really think it should not be used for more than symbols. ARIA and
Hi Dirk,
On Oct 7, 2013, at 12:36 AM, Dirk Schulze dschu...@adobe.com wrote:
I am all for accessibility! But isn't the idea to keep content out of CSS so
that it does not interfere with accessibility as much as possible?
The main problem with the 'content' property is that it is not
On 3 Oct 2013, at 4:46 am, Christian Biesinger cbiesin...@chromium.org wrote:
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Oct 1, 2013 at 4:53 PM, James Craig jcr...@apple.com wrote:
Follow-up question: Since this hasn’t made it into the CSS4 spec yet,
On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson d...@apple.com wrote:
On 3 Oct 2013, at 4:46 am, Christian Biesinger cbiesin...@chromium.org
wrote:
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Oct 1, 2013 at 4:53 PM, James Craig jcr...@apple.com wrote:
On 5 Oct 2013, at 6:22 am, Adam Barth aba...@webkit.org wrote:
On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson d...@apple.com wrote:
On 3 Oct 2013, at 4:46 am, Christian Biesinger cbiesin...@chromium.org
wrote:
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Oct
On Fri, Oct 4, 2013 at 1:37 PM, Dean Jackson d...@apple.com wrote:
On 5 Oct 2013, at 6:22 am, Adam Barth aba...@webkit.org wrote:
On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson d...@apple.com wrote:
On 3 Oct 2013, at 4:46 am, Christian Biesinger cbiesin...@chromium.org
wrote:
On Tue, Oct 1,
On 5 Oct 2013, at 6:45 am, Adam Barth aba...@webkit.org wrote:
Also, our prefixing/unprefixing rules are not set in stone. I think the
community
will evaluate them case by case.
I would encourage you (and others) not to ship new vendor-prefixed
APIs in production releases. If the
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Oct 1, 2013 at 4:53 PM, James Craig jcr...@apple.com wrote:
Follow-up question: Since this hasn’t made it into the CSS4 spec yet,
should we temporarily use “-webkit-alt” for the property name? I know there
has been
On Mon, Sep 30, 2013 at 10:56 PM, James Craig jcr...@apple.com wrote:
Did you realize you sent this off-list? Keeping my reply off-list, too.
Oops, I must have pressed the wrong button.
On Sep 30, 2013, at 10:42 PM, Ryosuke Niwa rn...@webkit.org wrote:
Are you going to add a build flag for
Follow-up question: Since this hasn’t made it into the CSS4 spec yet, should
we temporarily use “-webkit-alt” for the property name? I know there has been a
push to move away from vendor prefixes lately, so if there are no objections, I
propose we use the unprefixed version.
On Sep 30, 2013,
Sounds ok to add it prefixed.
- Maciej
On Oct 1, 2013, at 4:53 PM, James Craig jcr...@apple.com wrote:
Follow-up question: Since this hasn’t made it into the CSS4 spec yet, should
we temporarily use “-webkit-alt” for the property name? I know there has been
a push to move away from
On Tue, Oct 1, 2013 at 4:53 PM, James Craig jcr...@apple.com wrote:
Follow-up question: Since this hasn’t made it into the CSS4 spec yet,
should we temporarily use “-webkit-alt” for the property name? I know there
has been a push to move away from vendor prefixes lately, so if there are
no
14 matches
Mail list logo
