Closed Bug 628686 Opened 13 years ago Closed 12 years ago

Hitting return when summarizing article changes inserts bold text

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Tracking

(Not tracked)

RESOLVED WORKSFORME
2012.9

People

(Reporter: verdi, Assigned: Tobbi)

References

Details

(Whiteboard: u=contributor c=general p=1)

1. Submit an article for review 
2. Summarize your changes in the overlay dialog.
3. Hit enter or return on your keyboard instead of clicking the dialog button.
Result - '''Bold text''' will be inserted into your document.

Expected result: The submit button should be activated and no extra text should be inserted in the article.
I can confirm the effect (I found "Bold text" around very often in my translations) but I cannot confirm the way to reproduce it.

I mean, I think I have never used the keyboard but still the error happens. I will try to update the bug as soon as I find a way to have the error again.
I've seen similar behavior in other places where we use the editor toolbar. I think it is a matter of removing the toolbar buttons from the tab order (using tabindex?). This would also fix tabbing through the form fields to go straight to the textarea as expected.
Whiteboard: u=contributor c=general s=2012.4 p=1
Priority: -- → P3
Whiteboard: u=contributor c=general s=2012.4 p=1 → u=contributor c=general s=2012.5 p=1
Bumping to 2012.6.
Whiteboard: u=contributor c=general s=2012.5 p=1 → u=contributor c=general s=2012.6 p=1
Sprint based milestone :-)
Target Milestone: --- → 2012.6
Whiteboard: u=contributor c=general s=2012.6 p=1 → u=contributor c=general p=1
Target Milestone: 2012.6 → 2012.7
Target Milestone: 2012.7 → 2012.8
Target Milestone: 2012.8 → 2012.9
Tobbi looked at this a bit and wasn't able to repro. I just tried on stage and hitting enter from the change summary box submits the form as expected and I don't see any '''Bold text''' in the edit.
Assignee: nobody → tobbi.bugs
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.