Closed Bug 6647 (css2outline) Opened 25 years ago Closed 19 years ago

CSS2 'outline' property

Categories

(Core :: CSS Parsing and Computation, enhancement, P3)

enhancement

Tracking

()

VERIFIED DUPLICATE of bug 281972
Future

People

(Reporter: ian, Assigned: roc)

References

(Depends on 2 open bugs, Blocks 1 open bug, )

Details

(Keywords: access, css2, testcase, Whiteboard: [Hixie-P0][Hixie-PF])

The CSS2 outline property would allow widget focus to be drawn using
spec compliant methods.

There is a test page here:
   http://www.bath.ac.uk/%7Epy8ieh/internet/eviltests/outline.html

See bug 1859.
Priority: P3 → P5
Assignee: peterl → karnaze
Component: Style System → Widget Set
The property data is ready for use in the style context.
Assignee: karnaze → pierre
Reassigning to Pierre.
Status: NEW → ASSIGNED
Target Milestone: M8
*** Bug 7291 has been marked as a duplicate of this bug. ***
Blocks: 1859
Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze.  Widget Set component will be retired
shortly.
This should be implemented for frames in general. It is not a form element
specific bug. The CSS border rendering code needs to be modified to include
support for rendering the outline border.
Target Milestone: M9 → M11
I'm leaving 3 weeks on vacation. Pushing M9 bugs to M11.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 9816 ***
Status: RESOLVED → VERIFIED
Verified dup of #9816
Since bug 9816 turned into the 'remove CSS2 for FCS' bug, and is already 
littered with comments, I think we should make this the bug for FUTURE support 
of the 'outline' property.

Ian's comments from bug 9816 about remaining issues:

1. It appears that we don't support 'dotted' and 'dashed' outline-styles at all.
   This is wrong, IIRC we should treat them as 'solid' if we are not able to
   actually treat them as dotted or dashed styles (BUT I MAY BE WRONG THIS NEEDS
   TO BE CHECKED!!!).

2. We do not appear to support the 'invert' outline-color.

3. We have major drawing errors with inset and outset outline-styles.

4. We have some odd, annoying repaint problems (as I understand it, this is
   quite a major problem code-wise). This is bug 9809, marked Future, mostfreq.

5. We interpret 'groove' and 'ridge' the wrong way round.

6. We do not support outline on inline elements (the main use of outline!!!)

7. We draw the outline in the wrong place (as far as I can tell?).

8. According to bug 22892, we don't do 'outline' on XUL -- which I would 
   guess is one of the major uses of outline as far as we are concerned
Severity: enhancement → normal
Status: VERIFIED → REOPENED
Keywords: css2
Priority: P5 → P3
Resolution: DUPLICATE → ---
Target Milestone: M11 → Future
Summary: CSS2 'outline' property → CSS2 'outline' property [outline]
Taking QA per managerial policy.
QA Contact: chrisd → py8ieh=bugzilla
Blocks: 57270
Blocks: 55676
*** Bug 67966 has been marked as a duplicate of this bug. ***
Summary: CSS2 'outline' property [outline] → [outline]CSS2 'outline' property
Status: REOPENED → ASSIGNED
Blocks: 53927
Blocks: 58456
Depends on: 9809
Severity: normal → enhancement
Nominating this bug for nsbeta1 on behalf of gerardok@netscape.com.
Keywords: nsbeta1
Whiteboard: [Hixie-PF]
--> Style System (which may not be correct, but this sure ain't a Form Controls bug)
Component: HTML Form Controls → Style System
Keywords: access, fcc508
Blocks: 104166
Whiteboard: [Hixie-PF] → [Hixie-P0][Hixie-PF]
To implement we would need to be able to draw to the outside of the frame. This
would require some major modifications.
Marking nsbeta1-.
Keywords: nsbeta1nsbeta1-
No longer blocks: 58456
Depends on: 110143
Depends on: 151375
Assigning pierre's remaining Style System-related bugs to myself.
Assignee: pierre → dbaron
Status: ASSIGNED → NEW
Blocks: 22892
Blocks: 92286
Just curious: why does -moz-outline work, but the standard outline does not?
They have the same effect as far as I can tell.
Jerry: The reasons are listed in comment #9. This feature is just not ready for
the prime time. 

Sorry for the spam.
9. We don't merge outlines for inline elements correctly (bug 133165)
*** Bug 189464 has been marked as a duplicate of this bug. ***
Depends on: 21354
Taking.
Assignee: dbaron → roc+moz
*** Bug 21354 has been marked as a duplicate of this bug. ***
seems like the current -moz-outline is rendered inside the border but the web
standards outline property should be rendered over the border.
Alias: outline
Keywords: testcase
Summary: [outline]CSS2 'outline' property → CSS2 'outline' property
Blocks: 110143
No longer depends on: 110143
Keywords: nsbeta1-
It's worth pointing out that this property is in the default HTML 4.0 stylesheet
(*:focus). Hence, Moz should support it at least enough that a designer can
manipulate the default setting or turn it off.
Blocks: 151375
No longer depends on: 151375
Depends on: 250269
No longer blocks: 151375
Depends on: 151375
Depends on: 111526
Keywords: sec508
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0?
*** Bug 22892 has been marked as a duplicate of this bug. ***
Depends on: 266122
-moz-outline-offset is now implemented
Negative offsets are allowed
Depends on: 269212
Depends on: 269213
No longer depends on: 269213
No longer blocks: 110143
Depends on: 110143
I think we're ready to turn this on with the real 'outline' name. I will write a
style system patch to do that.
Status: NEW → ASSIGNED
See bug 93156 for the aliasing stuff I did for -moz-opacity, which you'll want
here as well, I suspect.
Yep. Thanks mats!

*** This bug has been marked as a duplicate of 281972 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Alias: outline → css2outline
You need to log in before you can comment on or make changes to this bug.