Closed Bug 444580 Opened 17 years ago Closed 17 years ago

chromeAccess and contentAccess both set to "2" by default

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: looris, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; it; rv:1.9) Gecko/2008061004 Firefox/3.0 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; it; rv:1.9) Gecko/2008061004 Firefox/3.0 from http://kb.mozillazine.org/Ui.key.contentAccess <blockquote>It’s a good idea to keep this preference set to a different value than ui.key.chromeAccess for the reasons mentioned above.</blockquote> instead, I installed FF3 on a brand new MacBook (there was no previous FF installation here) and they were both set to 2 by default. Reproducible: Always
Component: Build Config → Keyboard: Navigation
Product: Firefox → Core
QA Contact: build.config → keyboard.navigation
This is intentional (see bug 207510 comment #16). -> INVALID Please file a new bug, though, should the current settings actually clash in specific cases and hinder you from using certain websites.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.