Closed Bug 1061 Opened 26 years ago Closed 24 years ago

nested quotes not yet supported (<q> CSS quoting)

Categories

(Core :: Layout, enhancement, P2)

enhancement

Tracking

()

VERIFIED DUPLICATE of bug 24861
Future

People

(Reporter: kipp, Unassigned)

References

()

Details

(Keywords: css2, helpwanted, Whiteboard: hit during nsbeta2 standards compliance testing)

Attachments

(1 file)

[This is just a reminder: peter, reassign this to kipp when you have implemented
the css2 content attributes - thanks]
Status: NEW → ASSIGNED
*** Bug 1138 has been marked as a duplicate of this bug. ***
Summary: Q tag not yet supported → The Q element is not yet supported
Note.
For the Q element's ua.css declaration, the :before and :after
pseudo-elements and the quotes property will be needed, as well
as the content property mentioned above.

(Subtly altered summary so that this bug is easier to find using
a regexp search in a bugzilla query.)
Added URI of duplicate bug (1138)
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
QA Contact: 4144 → 4082
claudius,re-assigning some of Greg's open bugs to you.
Assignee: peterl → kipp
Status: ASSIGNED → NEW
CSS2 content properties are now in the style context
Assignee: kipp → troy
Status: NEW → ASSIGNED
Target Milestone: M4 → M5
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → REMIND
Q tag is implemented, and it uses :before (content: open-quote) and :after
(content: close-quote) specified in ua.css

We also pay attention to the 'quotes' property to determine what to display for
the quotes.

I'm marking this REMIND, because the remaining piece of work to do is to handle
nested quotes. We may, or may not, do this for the first version
Just out of interest, how difficult is the nesting thing to do?
The basic code is pretty easy to write, although it requires some changes to
pass the quote nesting level down as we recurse the content model. That's a
couple of days of work. The much larger piece of work is making it work
incrementally as the content model (or style info) changes. That's probably a
week to a week and a half worth of work
Priority: P2 → P5
Ok. Reducing priority. I'm leaving the severity though, as this is a spec
compliance issue. The milestone may need to be changed.

A test page for nested quotes is available at:
   http://www.bath.ac.uk/%7Epy8ieh/internet/eviltests/content/2.html

BTW: When this is implemented, special care should be taken with absolute
positioning. I'm not sure if the spec is clear about this or not, but it seems
to me that the nesting level should *not* spill into absolutely positioned
content. This should probably be raised in www-style@w3.org.
Status: RESOLVED → VERIFIED
OS: Windows NT → All
Hardware: PC → All
Summary: The Q element is not yet supported → {css2} nested quotes not yet supported
Target Milestone: M5
[Missed M5. Removing target milestone. Updating summary.]

A test page for this is at:
   http://www.bath.ac.uk/%7Epy8ieh/internet/eviltests/content/2.html

Generated counter support is currently waiting in bug 3247.
Severity: normal → enhancement
Priority: P5 → P2
[Fixing severity/priority...]
*** Bug 5554 has been marked as a duplicate of this bug. ***
QA Contact: claudius → petersen
Keywords: css2
Migrating from {css2} to css2 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...
Blocks: html4.01
Summary: {css2} nested quotes not yet supported → nested quotes not yet supported
*** Bug 35700 has been marked as a duplicate of this bug. ***
Besides making sure nested quotes, don't forget implementing both the "lang" 
and "dir" attributes and their associated values. I hate to add more this 
implementation but support for International languages is part of Web 
accessibility. Being able to specify <Q lang="fr"> and have the quotation marks 
be based on &laquo; &raquo; or &lsaquo; &rsaquo; is quite important.

I have examples here:
http://www.zotgroup.com/development/test-suites/html401/nn60b1/q-element.html

I hope to have examples of actual usage with different languages soon.

W3C specs:
http://www.w3.org/TR/html401/struct/dirlang.html#language-info

The testcase attached to this bug includes examples in different languages.

*** Bug 35725 has been marked as a duplicate of this bug. ***
> Being able to specify <Q lang="fr"> and have the quotation marks 
> be based on &laquo; &raquo; or &lsaquo; &rsaquo; is quite important.

It would actually be wrong, quoting styles are based on the _surrounding_ 
language and not the language of the quote -- "oui", not <<non>>.

That relies on us supporting CSS2's ":lang" pseudo-class which I believe is not
likely to be implemented by Netscape engineers before First Customer Ship (FCS).
Status: VERIFIED → REOPENED
Resolution: REMIND → ---
Troy no longer with us; marking Future, helpwanted, reassigning to nobody.
Assignee: troy → nobody
Status: REOPENED → NEW
Keywords: helpwanted
Target Milestone: --- → Future
That should be nobody@mozilla.org, not netscape.com.
Assignee: nobody → nobody
As per meeting with ChrisD today, taking QA.
QA Contact: petersen → py8ieh=bugzilla
Keywords: correctness
Summary: nested quotes not yet supported → nested quotes not yet supported (<q>)
Whiteboard: hit during nsbeta2 standards compliance testing
*** Bug 45401 has been marked as a duplicate of this bug. ***
Summary: nested quotes not yet supported (<q>) → nested quotes not yet supported (<q> CSS quoting)

*** This bug has been marked as a duplicate of 24861 ***
Status: NEW → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → DUPLICATE
Verifying as duplicate of bug filed fifteen months after this one.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: