Advanced Property Editor should "propose" values

RESOLVED FIXED in seamonkey2.5

Status

SeaMonkey
Composer
RESOLVED FIXED
12 years ago
7 years ago

People

(Reporter: Ricardo Almeida, Assigned: neil@parkwaycc.co.uk)

Tracking

Trunk
seamonkey2.5
Bug Flags:
in-testsuite -

SeaMonkey Tracking Flags

(seamonkey2.3 wontfix, seamonkey2.4 fixed, seamonkey2.5 fixed)

Details

Attachments

(2 attachments)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

Advanced Property Editor could be more user-friendly by adapting the input field of the Value.

Reproducible: Always

Steps to Reproduce:
1. Right-click on a tag (in status bar, ex: body)
2. Select "Advance Properties"
3. Pick an attribute

Actual Results:  
Value is just a text field

Expected Results:  
Value should adapt to the required type. If it's a color it should allow to select a color through color picker, etc...
Can you reproduce with SeaMonkey v1.1.9 ?
Assignee: composer → nobody
QA Contact: composer
(Reporter)

Comment 2

10 years ago
(In reply to comment #1)
> Can you reproduce with SeaMonkey v1.1.9 ?

I don't know exactly what you want with this question (ex: knowing that I'm still alive and wish this feature ;)), but yes I can reproduce it as it was not yet implemented...
OS: Windows XP → All

Updated

7 years ago
Assignee: nobody → iann_bugzilla
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Hardware: x86 → All
Version: unspecified → Trunk

Updated

7 years ago
Severity: enhancement → normal

Comment 3

7 years ago
Created attachment 549753 [details] [diff] [review]
Fix advanced property editor

This patch:
* Makes the onChangeHTMLAttribute, onInputHTMLAttributeName and onInputHTMLAttributeValue functions take an argument and change js/xul to use them that way.
* Get onInputHTMLAttributeName to call onInputHTMLAttributeValue with the new value.
* Add onselect triggers to menulists to update the tree.
Attachment #549753 - Flags: review?(neil)
(Assignee)

Comment 4

7 years ago
Comment on attachment 549753 [details] [diff] [review]
Fix advanced property editor

So, the old code relied on old behaviour in that changing the focused element's value in script would still trigger input and change events. This no longer happens. To replace the input events you've used select events, although technically command events would be superior. To replace the change event you've forced the attribute to get set when picked from the menulist, but I'm not convinced that's a good idea, although I don't have a better idea than making no change and requiring the user to re-select the suggested value.

The rest of the patch appears to be irrelevant.
Attachment #549753 - Flags: review?(neil) → review-
(Assignee)

Comment 5

7 years ago
(In reply to comment #4)
> I don't have a better idea than making no change and requiring the user to
> re-select the suggested value.
Well, I guess we could stop suggesting a value...
(Assignee)

Comment 6

7 years ago
Created attachment 550368 [details] [diff] [review]
Possible patch [Checked: trunk Comment 8 & comm-aurora Comment 12]
Attachment #550368 - Flags: review?(iann_bugzilla)

Comment 7

7 years ago
Comment on attachment 550368 [details] [diff] [review]
Possible patch [Checked: trunk Comment 8 & comm-aurora Comment 12]

r=me, the main difference between this and what I'd started to come up with was the changes to the xul
Attachment #550368 - Flags: review?(iann_bugzilla) → review+

Updated

7 years ago
Assignee: iann_bugzilla → neil
(Assignee)

Comment 8

7 years ago
Pushed changeset a0adbb4addc8 to comm-central.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 9

7 years ago
Is this common code with mailnews "AdvancedProperty Editor?
If so, don't have a clue on what to look for given:
Bug summary="should propose values" vs. comment 5
(Assignee)

Comment 10

7 years ago
On old versions of Gecko, Composer's Advanced Properties dialog (also available in some places in HTML compose) would detect a selection from the attribute menulist and if it was one of a small set of known attributes (e.g. dir) then it would suggest a value from an editable menulist rather than the simple input field used for most attributes.

At some point the rules for change events on focused text elements whose value was changed by script changed and the dialog was no longer able to detect a selection from the menulist, allthough it was still able to detect an attribute name that was manually typed in.

This patch allows it to detect a selection from the menulist again although I wasn't able to completely duplicate previous behaviour in which the editable menulist would suggest a default value which would then be copied to the tree if the attribute was not immediately modified.

Updated

7 years ago
status-seamonkey2.3: --- → wontfix
status-seamonkey2.4: --- → affected
status-seamonkey2.5: --- → fixed
Flags: in-testsuite-
Target Milestone: --- → seamonkey2.5

Comment 11

7 years ago
Comment on attachment 550368 [details] [diff] [review]
Possible patch [Checked: trunk Comment 8 & comm-aurora Comment 12]

This would be good to get on comm-aurora too.
Attachment #550368 - Flags: approval-comm-aurora+

Comment 12

7 years ago
Comment on attachment 550368 [details] [diff] [review]
Possible patch [Checked: trunk Comment 8 & comm-aurora Comment 12]

http://hg.mozilla.org/releases/comm-aurora/rev/a9f91402bf4c
Attachment #550368 - Attachment description: Possible patch → Possible patch [Checked: trunk Comment 8 & comm-aurora Comment 12]

Updated

7 years ago
status-seamonkey2.4: affected → fixed
You need to log in before you can comment on or make changes to this bug.