Consider converting textboxes to input[type=text]

NEW
Unassigned

Status

()

P5
normal
4 months ago
12 days ago

People

(Reporter: ntim, Unassigned)

Tracking

(Depends on: 6 bugs, Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 months ago
I believe the textboxes don't provide more features than html input, most of the code in the textbox binding serves to forward attributes/events to the inner html input.

The only thing I would be worried about would be the "Edit" context menu. It seems to be working automatically for HTML inputs when used in-content (even in XUL docs), I'm simply not sure whether it works in the top-level browser window, hence the suggestion to start only with the in-content ones.
(Reporter)

Comment 1

4 months ago
For the top-level browser window, if the context menu turns out not to work, it should be possible to use a customized built-in HTML input like bug 1437641 is doing.
(Reporter)

Updated

4 months ago
Depends on: 1437641
(Reporter)

Updated

4 months ago
Depends on: 1513337
(Reporter)

Updated

4 months ago
Depends on: 1513343
(Reporter)

Updated

3 months ago
Depends on: 1439679
(Reporter)

Updated

2 months ago
Depends on: 1521280
(Reporter)

Updated

2 months ago
Summary: Consider converting in-content textboxes to input[type=text] → Consider converting textboxes to input[type=text]
(Reporter)

Updated

a month ago
Depends on: 1528614
(Reporter)

Comment 2

a month ago

Now that the context menu stuff has been sorted out by bgrins (thanks!). Here’s a tentative plan:

  • make autocomplete and search-textbox independent from textbox
  • wait for quantumbar and remove legacy-urlbar
  • fold searchbar-textbox with the searchbar CE
  • fold urlbar behavior with UrlbarInput
  • convert all normal textboxes to input
(Reporter)

Updated

15 days ago
Depends on: 1534404
(Reporter)

Updated

15 days ago
Depends on: 1534455
You need to log in before you can comment on or make changes to this bug.