45459 - `Insert>HTML Source` is meaningless; should be "HTML..."

Status: VERIFIED FIXED

(Core :: DOM: Editor, defect, P4)

Description

[timeless]

NC4.73 uses Insert>HTML Tag...; Moz currently is spec'd for HTML Source...
It's ok to Edit html source, but it isn't ok to insert it. It's illogical and 
meaningless.
It would make sense to change `HTML Source...` to `Raw HTML...`.
If we did switch to &Raw HTML, we could have &Horizontal line which happens to 
match the other compose spec. Editor doesn't seem to have their spec on 
mozilla.org.

Otherwise we can return to `HTML Tags...` (note the `s`), this copies nc4's 
text but is somewhat inaccurate as you can insert plaintext.

Comment 1

[rubydoo123]

actually, using the term source is in line with other menu options such as view 
source, marking wontfix

Comment 2

[Asa Dotzler [:asa]]

I disagree.  Insert HTML source is confusing.  Insert|HTML Tags is much more
intuitive.  

Comment 3

[sujay]

verified in 7/21 build.

Comment 4

[Simon Fraser [no longer active]]

Reopening. We have menu items called "HTML Source..." in three (3) different 
menus right now. This is way confusing, and it needs fixing.

Comment 5

[Kathleen :Brade]

shorten summary; I agree about "HTML Source..." being used in way too many menus.
And why does it have the ellipsis after all of them?  I don't think any of them 
should have the dots except the Insert menu item (which could be arguable).

I propose we also delete Edit | HTML Source and keep "View | HTML Source" 
(consistent with browser).

Comment 6

[rubydoo123]

View  | HTML Source must function exactly like the View | HTML Source in the 
browser.

Edit | HTML Source is our method for editing the HTML source.

If anything gets dropped it will be the insert string. That should have been 
dropped anyway. The Edit | HTML Source will stay.

We will not use the term tags, it is inappropriate terminology, you would need 
to use the term "HTML element tags," which is just too long of a string to use 
in a menu item. HTML Source is consistent with the other terms as I stated 
earlier.

Comment 7

[Simon Fraser [no longer active]]

Having two menu items with the same name which have different functions (albeit 
on different menus) is really poor UI. Uses remember how to get to things by the 
name of the menu item; they don't always remember where something is; they'll 
cruise the menus until they find it. We *have* to come up with divergent names 
for these two items.

Comment 8

[rubydoo123]

setting to nsbeta3+

Comment 9

[rubydoo123]

adding priority to status whiteboard

Comment 10

[Kathleen :Brade]

We have decided for now to go with Insert | HTML...
fix checked in early this morning.

Comment 11

[sujay]

verified in 8/9 build.