AX: Implement CSS -webkit-alt property
https://bugs.webkit.org/show_bug.cgi?id=120188
This is blocking 20+ bugs on one of our higher profile content sites and we’d
like to start work on it. To clarify, the problem is that with CSS generated
content in pseudo-elements like this:
.expanda
On Mon, Sep 30, 2013 at 10:56 PM, James Craig 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 wrote:
>
> Are you going to add a build flag for this feature?
>
> For the fea
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, a
Sounds ok to add it prefixed.
- Maciej
On Oct 1, 2013, at 4:53 PM, James Craig 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 la
On Tue, Oct 1, 2013 at 4:53 PM, James Craig 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 objections, I
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa wrote:
> On Tue, Oct 1, 2013 at 4:53 PM, James Craig 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 3 Oct 2013, at 4:46 am, Christian Biesinger wrote:
> On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa wrote:
>> On Tue, Oct 1, 2013 at 4:53 PM, James Craig wrote:
>>>
>>> Follow-up question: Since this hasn’t made it into the CSS4 spec yet,
>>> should we temporarily use “-webkit-alt” for the
On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson wrote:
> On 3 Oct 2013, at 4:46 am, Christian Biesinger
> wrote:
>> On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa wrote:
>>> On Tue, Oct 1, 2013 at 4:53 PM, James Craig wrote:
Follow-up question: Since this hasn’t made it into the CSS4 sp
On 5 Oct 2013, at 6:22 am, Adam Barth wrote:
> On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson wrote:
>> On 3 Oct 2013, at 4:46 am, Christian Biesinger
>> wrote:
>>> On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa wrote:
On Tue, Oct 1, 2013 at 4:53 PM, James Craig wrote:
>
> Follow
On Fri, Oct 4, 2013 at 1:37 PM, Dean Jackson wrote:
> On 5 Oct 2013, at 6:22 am, Adam Barth wrote:
>> On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson wrote:
>>> On 3 Oct 2013, at 4:46 am, Christian Biesinger
>>> wrote:
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa wrote:
> On Tue, Oct 1
On 5 Oct 2013, at 6:45 am, Adam Barth 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 feature isn't s
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 clas
Hi Dirk,
On Oct 7, 2013, at 12:36 AM, Dirk Schulze 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 accessible.
> Why I
On Oct 7, 2013, at 11:55 PM, Chris Fleizach wrote:
> Hi Dirk,
>
>
> On Oct 7, 2013, at 12:36 AM, Dirk Schulze 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 proble
> On Oct 8, 2013, at 1:02 AM, Dirk Schulze 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 other screen r
15 matches
Mail list logo