Closed Bug 680852 Opened 13 years ago Closed 12 years ago

GCLI fields should support setting '<input required ...>' from parameter.isDataRequired()

Categories

(DevTools Graveyard :: Graphic Commandline and Toolbar, defect, P3)

Product:
DevTools Graveyard
Component:
Graphic Commandline and Toolbar
Platform:
x86_64
Windows 7
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jwalker, Unassigned)

Details

Sounds easy, except that fields don't have access to the parameter (because it's not 1-1 between fields and parameters due to array parameters) To date we've resisted pushing the parameter around anyway. This route could cause nasty cases later. It's probably better to add 'isDataRequired' as an argument to the (already slightly too long) Field constructor. Maybe we need to get into an options structure to cure this?
Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.
Component: Developer Tools → Developer Tools: Console
Triage. Filter on PEGASUS.
Priority: -- → P3
No longer blocks: GCLI-FUTURE
New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"
Component: Developer Tools: Console → Developer Tools: Graphic Commandline and Toolbar
We experimented with this in the bug680852-require branch, however it wasn't successful because "it's inconsistent (select not supported) and fairly ugly, and not functional because we don't have a form". Also we don't use ArgFetch anymore anyway.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.