TB captures shortcut keys, like 'a' for archive, even though the focus and input is in a web page form element. Cannot comment on posts in wordpress blogs

NEW
Unassigned

Status

Thunderbird
Mail Window Front End
4 years ago
2 years ago

People

(Reporter: alexkalderimis, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.94 Safari/537.36

Steps to reproduce:

I visited a blog post on a wordpress powered site. The feed opened up in the HTML reader. After reading I entered a comment in the comment box (successfully). When happy with the comment, I then went to enter my email address in the email form field below. I entered the first character of my email address: "a"


Actual results:

The post was 'archived', clearing the comment field I had entered and hiding the post from the feed history in the archive.


Expected results:

The form field should have supressed the archive action and allowed me to enter my email address.

Comment 1

2 years ago
I shouldn't think that this would work - but I know zero about rss
Component: Untriaged → Feed Reader
Product: Thunderbird → MailNews Core
Version: 31 Branch → 31

Comment 2

2 years ago
This doesn't have anything to do with feeds, it's due to Tb capturing shortcut keys, like 'a' for archive, even though the focus and input is in a web page form element.  The key handler should skip such key events.  Other than this intercept, since js is enabled in web pages, posting comments in forms inline should work nicely.
Status: UNCONFIRMED → NEW
Component: Feed Reader → Mail Window Front End
Ever confirmed: true
Product: MailNews Core → Thunderbird
Version: 31 → unspecified

Updated

2 years ago
Summary: Cannot comment on posts in wordpress blogs → TB captures shortcut keys, like 'a' for archive, even though the focus and input is in a web page form element. Cannot comment on posts in wordpress blogs

Updated

2 years ago
Duplicate of this bug: 327252
You need to log in before you can comment on or make changes to this bug.