Closed
Bug 51688
Opened 25 years ago
Closed 23 years ago
Use Stylesheet menu: differentiate "None" from disabling all styles
Categories
(SeaMonkey :: General, defect, P3)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0
People
(Reporter: burnus, Assigned: fantasai.bugs)
References
Details
Attachments
(1 file, 2 obsolete files)
|
2.01 KB,
patch
|
mpt
:
review+
alecf
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
Hi this is with 2000-09-06-21/Linux and a strip off from a bug reported in 6782.
The menu item View|Use stylesheet|None should be changed in order to reflect
that "None" doesn't disable the stylesheets totally, but only those that are in
a external file.
Suggested menu entry "Minimal Page Style"
| Reporter | ||
Comment 1•25 years ago
|
||
The entry might be changed back to "None" if bug 51690 is solved or both entries
should be available.
There have been many other proposals for how to differentiate between turning
off all preferred and alternate stylesheets and turning off all author styles.
See the long discussion on bug 6782.
Comment 3•25 years ago
|
||
*** This bug has been marked as a duplicate of 6782 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Splitting up bug 6782 ("UI for alternate and user stylesheets").
"One bug report == one issue is one of the golden rules of Bugzilla because it
enables independent tracking and prioritization of each issue."
-- ekrock@netscape.com, bug 4510
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
I don't think the change in the title of this bug is the right solution, so I'm
retitling it. The problem is that we need to differentiate "None" from
disabling all author styles (which should probably disable stylistic attributes
in HTML just as much as persistent CSS stylesheets).
Summary: Use Stylesheet menu: change "None" to "Minimal Page Style" → Use Stylesheet menu: differentiate "None" from disabling all styles
Comment 7•24 years ago
|
||
*** This bug has been marked as a duplicate of 32372 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → DUPLICATE
This needs to be tracked separately. If bug 51690 doesn't get fixed for Moz1.0,
then this really should. If 51690 does get fixed, we can WONTFIX this.
And anyway, it's not a duplicate: this isn't about providing a 'disable
stylesheets' option, it's about marking the 'disable alternate & preferred
stylesheets' option as such, instead of as "none". I'll admit it's in the wrong
component, though--moving to UI Design.
If you want this off your list, Pierre, assign it to me. I think I can handle a
string change, if it comes to that. :)
Status: RESOLVED → REOPENED
Component: Style System → User Interface Design
Keywords: mozilla1.0
Resolution: DUPLICATE → ---
Comment 9•23 years ago
|
||
I did not want to have a bug just for renaming a string, I thought it could be
part of bug 32372. But you're right: let's keep the bug open because we still
haven't decided on a UI. We have at least two possibilities:
1) Have separate settings: a pref to disable all styles and a menu item in the
Stylesheet menu to disable just the linked stylesheets.
2) Merge the two settings: make the menu item reflect the pref's state and
disable all styles.
| Assignee | ||
Comment 10•23 years ago
|
||
> 1) Have separate settings: a pref to disable all styles and a menu item in the
> Stylesheet menu to disable just the linked stylesheets.
I should be able to disable all author-level styles on a page-by-page basis--and
that implies not in the prefs.
> 2) Merge the two settings: make the menu item reflect the pref's state and
> disable all styles.
So, if I disable all author-level styles in the prefs, and then enable them in
the menus, what happens?
I don't think we need a pref for this--the menu item should do. I doubt many
people will want to browse with the entire author cascade level disabled all the
time. :)
Comment 11•23 years ago
|
||
the menu should override the pref I guess
Comment 12•23 years ago
|
||
Moving to mozilla1.1. Engineers are overloaded!
Target Milestone: mozilla0.9.9 → mozilla1.1
Comment 14•23 years ago
|
||
Bulk moving from Moz1.1 to future-P1. I will pull from this list when scheduling
work post Mozilla1.0.
Priority: P3 → P1
Target Milestone: mozilla1.1 → Future
| Assignee | ||
Comment 15•23 years ago
|
||
> Moving to mozilla1.1. Engineers are overloaded!
I'm not, though, so I'm taking this, if Pierre doesn't mind. :)
Assignee: pierre → fantasai
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Priority: P1 → P3
Target Milestone: Future → mozilla1.0
| Assignee | ||
Comment 16•23 years ago
|
||
| Assignee | ||
Comment 17•23 years ago
|
||
Another option is to change the wording to "Basic Page Style".
| Assignee | ||
Comment 18•23 years ago
|
||
| Assignee | ||
Comment 19•23 years ago
|
||
Added accesskey, as requested by mpt
Attachment #75824 -
Attachment is obsolete: true
Attachment #75922 -
Attachment is obsolete: true
Comment 20•23 years ago
|
||
Comment on attachment 75947 [details] [diff] [review]
patch v3
r=mpt, on the understanding that this is a temporary measure until `No Author
Styles' is implemented
Attachment #75947 -
Flags: review+
Comment 21•23 years ago
|
||
Comment on attachment 75947 [details] [diff] [review]
patch v3
sr=alecf
Attachment #75947 -
Flags: superreview+
Comment 22•23 years ago
|
||
Comment on attachment 75947 [details] [diff] [review]
patch v3
not sure when mpt became a reviewer. assuming that alecf's sr counts as an r=
and this has brendan's rubberstamp for wording only changes. a=asa (on behalf
of drivers) for checkin to the 1.0 trunk
Attachment #75947 -
Flags: approval+
Comment 23•23 years ago
|
||
The menu access key (B) shows on altenate stylesheet as well as
preferred style sheet.
http://www.bristol.ac.uk/is/selfhelp/documentation/docs-g1/docs-g1.htm
Comment 24•23 years ago
|
||
has this landed yet? time is running out.
| Assignee | ||
Comment 25•23 years ago
|
||
checkin by timeless Mar 26 19:17
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → FIXED
Comment 26•23 years ago
|
||
I don't think the problem it caused with access keys has been fixed though.
Go to http://www.w3.org/Style/CSS/
View/Use Style and (in Win2K at least) you get underlined Bs
all over the place.
(Admittedly this is on a 20020328 build because of Easter break)
Comment 27•23 years ago
|
||
Sorry - found it as bug 133842
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•