Closed Bug 89557 Opened 21 years ago Closed 10 years ago

Visible prefs to control frames (Accessibility improvements)

Categories

(SeaMonkey :: Preferences, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: tvalusek, Unassigned)

References

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

Details

(Keywords: access, Whiteboard: [2012 Fall Equinox])

I'm using the Net since 1997, and since I'm visually impaired, I work with 
modified browser settings (larger font).Some web design issues make my browsing 
difficult, and I'd like Mozilla to allow me force some kind of behavior which 
could help me to browse the Web more comfortably.

1. I'd like to disallow the "No" value of scrolling and resize attributes of 
FRAME tag. Often the text doesn't fit into frame and scrolling and resizing are 
disabled by an author.

2. I'd like to force the CSS attribute "Overflow" to "auto", so that if a 
content of an element overflows from its space, the browser would provide a 
scrollbar(s) to view complete content.

3. I'd like to teel the browser not to overlap text with other objects 
(demonstration: in 800x600 resolution, set the text size to 200% and navigate 
to http://pes.eunet.cz). This mainly happens when the value of "align" 
attribute is set to "right", and the element on the left is larger than the 
room left to the left of right-aligned image/table.
These are also good suggestions, but probably would be better if they were 
separate bugs. I'd particularly like a way to do 1 after the page has 
loaded, but I can also see that it might be desirable as a pref. Perhaps 1 
and 2 can be done through the DOM?
Can't 2 be accomplished by setting an "!important" rule in the user stylesheet?
Open the file chrome/userContent.css in your Mozilla profile...

For #2, add the rule "* { overflow: auto !important}"

For #3, add the rule "* { clear: both }" (this will prevent floating or
"aligned" elements" from being overlapped.  It will not help with absolutely
positioned elements.  You could also add "* { position: static }", I guess).
The clear rule probably does not need to be !important, but it could be...

Note that solving #2 should also solve the 'scrolling="no"' problem from #1,
since they use the same mechanism.

For a further solution to #1, one could use a bookmarklet that grabs all the
<frame> and <iframe> elements from the DOM and resets their resize attributes. 
This could even happen automatically if bug 89016 is fixed.

Tomas, I'd suggest that whatever problems you see after trying these suggestions
be filed as separate bugs (one bug per problem).  This bug can depend on all of
those and be used to track them.

Also, let me know if you find the CSS suggestions I made useful.  If so, we
could try to add them (commented out) to the default userContent.css so people
will be more likely to find them.
er, correction.  "* { position:static}" will do nothing useful.  You want "* {
position: static !important}" if you decide to override positioning.
Tomas, have you had a chance to try those suggestions?  If so, please file any
issues not solved by those as separate RFEs that block this bug....
Moving this to User Design in the mean time..good suggestions. Let them sort it
out from there.
Assignee: kmcclusk → mpt
Status: UNCONFIRMED → NEW
Component: Compositor → User Interface Design
Ever confirmed: true
QA Contact: petersen → zach
Keywords: access
Cool. These were already a part of my `Multimedia' prefs panel design, as 
follows:

+--------------------------------------------------------------------+
| Navigator Preferences :::::::::::::::::::::::::::::::::::::::::::::|
+--------------------------------------------------------------------+
|                                                                    |
| +-------------------+ Multimedia ::::::::::::::::::::::::::::::::: |
| | Languages         |                                              |
| | Identity          | [/] Automatically load ima_ges and plugins   |
| | Connection        |     [/] Allow images as _backgrounds         |
| | Helper Apps       | [/] Allow images to _animate                 |
| | Start Pages       |     [/] Allow _looping of animations         |
| | History & Cache   | [/] Play _sounds                             |
| | Fonts             |     [/] Allow loo_ping of sounds             |
| | Colors & Effects  | [/] Display normal _frames                   |
| |:Multimedia::::::::| [/] Display _in-line frames                  |
| | Scripts & Windows | [ ] Always allow frame _resizing             |
| | Privacy           | [ ] Always allow frame _scrolling            |
| | Appearance        | ( Filters ... ) There are no filters active. |
| | System            |                                              |
| +-------------------+ :::::::::::::::::::::::::::::::::::::::::::: |
|                                                                    |
| [?]                                          ( Cancel ) ((  OK  )) |
+--------------------------------------------------------------------+

This can be the bug for the GUI; I've filed or found blocking bugs for the 
back-end prefs. --> Preferences
Assignee: mpt → doronr
Component: User Interface Design → Preferences
Depends on: 24418, frame-off, 105796, 105797
QA Contact: zach → sairuh
Summary: Accessibility improvements → Visible prefs to control frames (Accessibility improvements)
Product: Browser → Seamonkey
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: UNCONFIRMED → NEW
Ever confirmed: true
As original reported didn't answer on comments 3-5 I'm closing this. If you still interesting in implementing any parts of this bug fill separate bugs for each suggestion
Assignee: doronr → nobody
Status: NEW → RESOLVED
Closed: 10 years ago
QA Contact: bugzilla
Resolution: --- → INCOMPLETE
Whiteboard: [2012 Fall Equinox]
You need to log in before you can comment on or make changes to this bug.