bug report: Value Error: content Parse Error attr(title)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

bug report: Value Error: content Parse Error attr(title)

Jens Sadowski
The following finding seems to be a bug (and did not show up before very recently):
   Value Error : content Parse Error  attr(title)

The CSS line looks as this:
   a[title].pagenum:after { ... }

The same without the :after goes through without this message.


Reply | Threaded
Open this post in threaded view
|

Re: bug report: Value Error: content Parse Error attr(title)

David Dorward-3

On 24 Jun 2015, at 4:58, Jens Sadowski wrote:

The following finding seems to be a bug (and did not show up before very recently):
Value Error : content Parse Error attr(title)

The CSS line looks as this:
a[title].pagenum:after { ... }

The same without the :after goes through without this message.

I typed a[title].pagenum:after { display: block } into the Direct Input field and it passed without a problem.

Can you provide a reproducible test case?

--
David Dorward
http://dorward.co.uk/


signature.asc (886 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: bug report: Value Error: content Parse Error attr(title)

David Dorward-3
In reply to this post by Jens Sadowski

On 24 Jun 2015, at 9:47, Jens Sadowski wrote:

Hi David,

thanks for looking into this. You can try this URL:

http://www.gutenberg.org/files/49218/49218-h/49218-h.htm

This file was uploaded to Gutenberg on June 15 and went without any error message through the CSS validator then but not any longer.

I can reproduce the problem with:

:after { content: attr(title); }

I'm pretty sure that is valid and we have a bug here.

--
David Dorward
http://dorward.co.uk/


signature.asc (886 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: bug report: Value Error: content Parse Error attr(title)

Ludo
Hi,
I have same problem with this :

a.tooltip:after{
....
  content: attr(data-tool);
....
}
 
(With or without :after)

If  content: "...";  it is valid
if  content: attr(title);  it is not valid

greetings
Ludo




Reply | Threaded
Open this post in threaded view
|

Re: bug report: Value Error: content Parse Error attr(title)

Jens Sadowski
In reply to this post by David Dorward-3
Hi David,

as you helped me to look into this in June: may I ask whether this bug will be fixed anytime in the future? Or is it not any longer valid CSS 2.1 and therefore not seen as a bug any longer?

Project Gutenberg get s a bit uneasy about this and starts to advise us uploaders to "repair" our CSS code if it generates error messages in the CSS validator irrespectively why...

Cheers,

Jens

--------------------------------------------
On Wed, 6/24/15, David Dorward <[hidden email]> wrote:

 Subject: Re: bug report: Value Error: content Parse Error attr(title)
 To: "Jens Sadowski" <[hidden email]>, [hidden email]
 Date: Wednesday, June 24, 2015, 10:53 AM
 
 
 On 24 Jun 2015, at 9:47, Jens Sadowski wrote:
 
 
 Hi David,
 
 thanks for looking into this. You can try this URL:
 
 http://www.gutenberg.org/files/49218/49218-h/49218-h.htm
 
 This file was uploaded to Gutenberg on June 15 and went
 without any error message through the CSS validator then but
 not any longer.
 
 
 I can reproduce the problem with:
 
 :after { content: attr(title); }
 
 
 I'm pretty sure that is valid and we have a bug
 here.
 
 --
 
 David Dorward
 
 http://dorward.co.uk/