Save ALT + S in FireFox 2.0!

[Jealousy10312]

I need your help!

I've submitted a bug report to FireFox about this problem. If you did not download the latest release candidate for FireFox 2.0, then you do not see my problem here. The fact of the matter is that if you do not vote & support this bug, then it will stay in FireFox 2.0.

In FireFox 2.0, when you hit ALT + S to post something in VBulletin, it opens up History > Back instead of posting it! I know many people like this feature, and if you want to save it, visit the below links to vote & view my bug report.

If you do not vote, the ALT + S feature has little chance of surviving FireFox 2.0!

Thanks for the support.

https://bugzilla.mozilla.org/show_bug.cgi?id=357589

VOTE TO SUPPORT HERE:

https://bugzilla.mozilla.org/votes.cgi?action=show_user&bug_id=357589#vote_357589

PROMOTE THE FIX BY USING THESE IN YOUR SIG:

http://parkyourfiles.net/uploads/ee8870492e.png

With Image:

[url="https://bugzilla.mozilla.org/votes.cgi?action=show_user&bug_id=357589#vote_357589"][IMG]http://parkyourfiles.net/uploads/ee8870492e.png[/IMG][/url]

Without Image:

Save ALT + S in FireFox 2.0!

Vote Now!

[b][color=Red]Save ALT + S in FireFox 2.0!

[url="https://bugzilla.mozilla.org/votes.cgi?action=show_user&bug_id=357589#vote_357589"]Vote Now![/url][/color]
[/b]

[filburt1]

I don't advocate the viewport having keyboard priority over its actions or its surrounding framework, so I won't support this either. WordPress is even more annoying: Alt-D, which should select the address bar in every Windows browser, inserts a datestamp instead.

[Jealousy10312]

Ok, well thanks for reading.

[Dean C]

There is another way of doing it, but for some reason it's slipped my mind.

[Quillz]

I need your help!

I've submitted a bug report to FireFox about this problem. If you did not download the latest release candidate for FireFox 2.0, then you do not see my problem here. The fact of the matter is that if you do not vote & support this bug, then it will stay in FireFox 2.0.

In FireFox 2.0, when you hit ALT + S to post something in VBulletin, it opens up History > Back instead of posting it! I know many people like this feature, and if you want to save it, visit the below links to vote & view my bug report.

If you do not vote, the ALT + S feature has little chance of surviving FireFox 2.0!

Thanks for the support.

https://bugzilla.mozilla.org/show_bug.cgi?id=357589

VOTE TO SUPPORT HERE:

https://bugzilla.mozilla.org/votes.cgi?action=show_user&bug_id=357589#vote_357589

PROMOTE THE FIX BY USING THESE IN YOUR SIG:

http://parkyourfiles.net/uploads/ee8870492e.png

With Image:



Without Image:

Save ALT + S in FireFox 2.0!

Vote Now!

Surely you realize this default behavior can be reverted, right?

Simply type in "about:config" on the address bar and find these two values: ui.key.chromeAccess and ui.key.contentAccess. By default, the former says "4" and the latter says "5." Just reverse the two values to restore the former default behavior. It's a simple fix.

[Colin F]

It's a relatively simple fix, but I agree that it's annoying.

[Scott MacVicar]

Or just use Shift + Alt + S

[Raz Meister]

Or Tab -> Enter

[Dean C]

Or just use Shift + Alt + S

I knew there was another

[phill2003]

I dont understand? this alt s bit when i do it nothing gets put into a thread lol how does it work?

[Quillz]

I dont understand? this alt s bit when i do it nothing gets put into a thread lol how does it work?

It's a quick way of submitting a post, but by default, Firefox 2.0 uses the hotkeys to access the history menu. I posted earlier how to revert the behavior.

[BamaStangGuy]

Or Tab -> Enter

This is what I do. Alot easier than Alt + S

[user02934123123]

As an aside to this topic, I've recently installed firefox 2.0 on one of our test machines, and notice that the access keys in vB seem altogether not to work (e.g. ALT+2 for New Message search, etc.) -- while they worked fine in firefox 1.5. Does anyone know why / a workaround?

[Scott MacVicar]

shift + alt + 2

[JGNYC]

In the address bar type about:config

change ui.key.chromeAccess to 5
change ui.key.contentAccess to 4

Restart FF