Community
Participate
Working Groups
I don't remember if there was a bug opened about this, but search is not cooperating... When you change you bug attribute, like target milestone, after submit, the combo is not highlighted like new incoming comments and other read-only attributes.
If the change was made by you, after submission, the attribute shouldn't be highlighted since the change was made by you. Only changes made by others should appear highlighted in the editor. Are you expecting different behaviour?
(In reply to comment #1) > If the change was made by you, after submission, the attribute shouldn't be > highlighted since the change was made by you. Only changes made by others > should appear highlighted in the editor. Are you expecting different behaviour? > There is something strange here. I opened this bug because I marked a bug as RESOLVED FIXED and set the milestone. It was on a 1.0.1 release, I think. On this case, on editor automatic reopen, the Status and Resolution fields were highlighted, but Target Milestone wasn't. I just tried on 20070214-1830 M5 dev-build, and happened what you said: nothing was highlighted. Was this a proposital change? I liked the old behavior.
Yes, the editor should now only highlight incoming changes (but not those submitted by you). Although currently (M1) upon submission of a new comment it will appear with the highlighted (but this is a 'bug').
Was there some motivation to have the old behavior "fixed"? I like the old highlighting policy because it gives me the feedback that my changes were persisted.
There is also issue with editor collapsing all sections after submission. I think it should restore expanded sections, scroller position and focus location after submission or task refresh.
(In reply to comment #5) > There is also issue with editor collapsing all sections after submission. I > think it should restore expanded sections, scroller position and focus location > after submission or task refresh. See bug#172033 (In reply to comment #4) > Was there some motivation to have the old behavior "fixed"? > I like the old highlighting policy because it gives me the feedback that my > changes were persisted. This is sounds like a 'trust' issue no? I.e. you aren't shown the changes you made in the bugzilla web ui for example.
(In reply to comment #6) > > Was there some motivation to have the old behavior "fixed"? > > I like the old highlighting policy because it gives me the feedback that my > > changes were persisted. > This is sounds like a 'trust' issue no? I.e. you aren't shown the changes you > made in the bugzilla web ui for example. I may agree with Willian in case if comment been submitted trough the web UI. I often do that and then see the same issue in Mylar.
(In reply to comment #3) > Yes, the editor should now only highlight incoming changes (but not those > submitted by you). Although currently (M1) upon submission of a new comment it > will appear with the highlighted (but this is a 'bug'). The same happens when you submit a patch. (In reply to comment #6) > This is sounds like a 'trust' issue no? I.e. you aren't shown the changes you > made in the bugzilla web ui for example. Yes, looks like something like this. Perhaps it is just a matter of getting used to this.
Well lets see. :) Feel free to reopen discussion if you still feel strongly about this after some more use.
