Closed
Bug 710110
Opened 13 years ago
Closed 7 years ago
Support min/max 'size' attributes for simple-prefs
Categories
(Add-on SDK Graveyard :: General, enhancement, P3)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: erikvvold, Unassigned)
References
Details
(Whiteboard: [lang=js] [lang=xul])
For string prefs one should be able to specifiy a min/max string length (or at least max length).
Also it may be possible to make the input size proportional to the max length.
Priority: -- → P3
Comment 1•12 years ago
|
||
Does this include implementing textareas / multiline inputs, or should I create a new bug for it? Comma-separated lists of words begin to be unreadable very quickly in those simple one-line inputs.
Comment 2•12 years ago
|
||
(In reply to Petr Janeček from comment #1)
> Does this include implementing textareas / multiline inputs, or should I
> create a new bug for it?
We'll need another bug for this.
> Comma-separated lists of words begin to be
> unreadable very quickly in those simple one-line inputs.
hmm, what kind of UI do you imagine for this?
Updated•12 years ago
|
Assignee: nobody → evold
Comment 3•12 years ago
|
||
(In reply to Erik Vold from comment #2)
> We'll need another bug for this.
Done, https://bugzilla.mozilla.org/show_bug.cgi?id=775892
> > Comma-separated lists of words begin to be
> > unreadable very quickly in those simple one-line inputs.
>
> hmm, what kind of UI do you imagine for this?
Huh. I don't really think that having a separate "list" preference type is worth the pain (because textarea is enough IMO), but once you asked, I mocked a quick example (based on Stack Overflow tag list, it was the first similar thing that caught my eye): http://i.imgur.com/2DGts.jpg
Would it be a reasonable feature with fair usage (read as "Should I create a bug for it?"), or is it too much?
Updated•12 years ago
|
Blocks: sdk/simple-prefs
Updated•12 years ago
|
Assignee: evold → nobody
Whiteboard: [good first bug]
Comment 4•11 years ago
|
||
currently the expected way to do this would be in options_xul.py, but since python code is going away (hopefully) soon, maybe this isn't a "good first bug", and also maybe it should be re-triaged..
Priority: P3 → --
Whiteboard: [good first bug]
Priority: -- → P3
Updated•10 years ago
|
Whiteboard: [good first bug] [lang=javascript] [lang=xul]
Updated•9 years ago
|
Whiteboard: [good first bug] [lang=javascript] [lang=xul] → [good first bug] [lang=js] [lang=xul]
Updated•8 years ago
|
Whiteboard: [good first bug] [lang=js] [lang=xul] → [lang=js] [lang=xul]
Comment 5•7 years ago
|
||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•