Closed
Bug 742777
Opened 13 years ago
Closed 13 years ago
A couple of minor tweaks to the Media Tab.
Categories
(SeaMonkey :: Page Info, defect)
SeaMonkey
Page Info
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philip.chee, Assigned: philip.chee)
Details
Attachments
(4 files, 3 obsolete files)
5.96 KB,
patch
|
neil
:
review+
ehsan.akhgari
:
review+
|
Details | Diff | Splinter Review |
21.94 KB,
image/png
|
Details | |
21.98 KB,
image/png
|
Details | |
5.82 KB,
patch
|
Details | Diff | Splinter Review |
Port the following Firefox PageInfo patches:
Bug 492250 - URLs in Page Info Media tab should be LTR.
Bug 573603 - Speed up Page Info > Media.
![]() |
Assignee | |
Comment 1•13 years ago
|
||
Well nothing looks broken but I don't know how to test.
And don't we need some css in the skin like?:
treechildren::-moz-tree-cell-text(ltr) {
direction: ltr !important;
}
Attachment #612602 -
Flags: feedback?(neil)
Comment 2•13 years ago
|
||
(In reply to Philip Chee from comment #1)
> And don't we need some css in the skin like?:
>
> treechildren::-moz-tree-cell-text(ltr) {
> direction: ltr !important;
> }
Bug 477902.
Updated•13 years ago
|
Attachment #612602 -
Flags: feedback?(neil) → feedback+
![]() |
Assignee | |
Updated•13 years ago
|
Attachment #612602 -
Flags: review?(neil)
Comment 3•13 years ago
|
||
Actually, I just noticed we need to fix the Links and Forms tabs too. Also, what about the URL fields such as Address(2×) and Referring URL?
![]() |
Assignee | |
Comment 4•13 years ago
|
||
> Actually, I just noticed we need to fix the Links and Forms tabs too.
Fixed.
> Also, what about the URL fields such as Address(2×) and Referring URL?
I think I'll ask Ehsan, he's the expert after all. Ehsan?
Attachment #612602 -
Attachment is obsolete: true
Attachment #612602 -
Flags: review?(neil)
Attachment #612900 -
Flags: ui-review?(ehsan)
Attachment #612900 -
Flags: review?(neil)
Comment 5•13 years ago
|
||
Comment on attachment 612900 [details] [diff] [review]
Patch v1.1 Fix Links and Forms tabs too.
[Sorry if these apply to the previous patch but I had only done a ui review.]
>+ this._ltrAtom = gAtomSvc.getAtom("ltr");
>+ this._brokenAtom = gAtomSvc.getAtom("broken");
I don't like this because it means that each view has their own reference to these atoms, even though they may never use them, and additionally I think I would prefer it if you override getCellProperties in the views that need it as this seems to be a better match for the code style in the rest of the file.
> getRowProperties: function(row, prop) { },
>- getCellProperties: function(row, column, prop) { },
>+
>+ getCellProperties: function(row, column, prop)
[getCellProperties was here because it was a dummy method. Now that it has a real body, you would need to move it before getRowProperties.]
>+ switch (column.element.id) {
FYI column.id works.
Attachment #612900 -
Flags: review?(neil) → review-
![]() |
Assignee | |
Comment 6•13 years ago
|
||
>>+ this._ltrAtom = gAtomSvc.getAtom("ltr");
>>+ this._brokenAtom = gAtomSvc.getAtom("broken");
> I don't like this because it means that each view has their own reference to
> these atoms, even though they may never use them, and additionally I think I
> would prefer it if you override getCellProperties in the views that need it
> as this seems to be a better match for the code style in the rest of the file.
Fixed.
>> getRowProperties: function(row, prop) { },
>>- getCellProperties: function(row, column, prop) { },
>>+
>>+ getCellProperties: function(row, column, prop)
> [getCellProperties was here because it was a dummy method. Now that it has
> a real body, you would need to move it before getRowProperties.]
Back to dummy.
>>+ switch (column.element.id) {
> FYI column.id works.
Fixed.
> Also, what about the URL fields such as Address(2×) and Referring URL?
Fixed.
Attachment #612900 -
Attachment is obsolete: true
Attachment #612900 -
Flags: ui-review?(ehsan)
Attachment #613116 -
Flags: ui-review?(ehsan)
Attachment #613116 -
Flags: review?(neil)
Comment 7•13 years ago
|
||
Comment on attachment 613116 [details]
Patch v1.2 Fix Address (x2) and Referer textboxes too.
text-align: right is a bad idea. If you want the text to be aligned to the right in LTR builds and to the left in RTL builds, you want text-align: end.
Also, please submit a screenshot in RTL and LTR modes in addition to the patch.
Attachment #613116 -
Flags: ui-review?(ehsan) → ui-review-
Comment 8•13 years ago
|
||
(In reply to Ehsan Akhgari from comment #7)
> text-align: right is a bad idea. If you want the text to be aligned to the
> right in LTR builds and to the left in RTL builds, you want text-align: end.
Unfortunately he also uses direction: ltr; so start and end will always be the same as left and right. I don't know what we can do about this.
![]() |
Assignee | |
Comment 9•13 years ago
|
||
Comment on attachment 613116 [details]
Patch v1.2 Fix Address (x2) and Referer textboxes too.
Yes sorry. Thinko on my part.
Attachment #613116 -
Flags: review?(neil)
![]() |
Assignee | |
Comment 10•13 years ago
|
||
> Ehsan Akhgari [:ehsan] 2012-04-07 10:03:38 PDT
> Comment on attachment 613116 [details]
> Patch v1.2 Fix Address (x2) and Referer textboxes too.
>
> text-align: right is a bad idea. If you want the text to be aligned to the
> right in LTR builds and to the left in RTL builds, you want text-align: end.
Fixed. Now using:
> +.urltext:-moz-locale-dir(rtl) {
> + direction: ltr !important;
> + text-align: end !important;
> +}
> Also, please submit a screenshot in RTL and LTR modes in addition to the
> patch.
Will do.
> Unfortunately he also uses direction: ltr; so start and end will always be
> the same as left and right. I don't know what we can do about this.
I intended to use |:-moz-locale-dir(rtl)| in the previous patch but somehow forgot to do so.
Attachment #613116 -
Attachment is obsolete: true
Attachment #613164 -
Flags: review?(neil)
Attachment #613164 -
Flags: review?(ehsan)
![]() |
Assignee | |
Comment 11•13 years ago
|
||
Attachment #613165 -
Flags: review?(ehsan)
![]() |
Assignee | |
Comment 12•13 years ago
|
||
Attachment #613166 -
Flags: review?(ehsan)
Comment 13•13 years ago
|
||
Comment on attachment 613164 [details] [diff] [review]
Patch v1.3 Fix LTR/RTL issues.
>+gImageView._brokenAtom = atomSvc.getAtom("broken");
>+gImageView._ltrAtom = atomSvc.getAtom("ltr");
>+gFormView._ltrAtom = atomSvc.getAtom("ltr");
>+gLinkView._ltrAtom = atomSvc.getAtom("ltr");
File style doesn't go with prefixes (either _ or m) so drop the _s please.
>- props.AppendElement(gBrokenAtom);
>+ props.AppendElement(this._brokenAtom);
Or you could always switch to gBrokenAtom and gLtrAtom ;-)
Attachment #613164 -
Flags: review?(neil) → review+
Updated•13 years ago
|
Attachment #613164 -
Flags: review?(ehsan) → review+
Updated•13 years ago
|
Attachment #613165 -
Flags: review?(ehsan)
Updated•13 years ago
|
Attachment #613166 -
Flags: review?(ehsan)
![]() |
Assignee | |
Comment 14•13 years ago
|
||
>>+gImageView._brokenAtom = atomSvc.getAtom("broken");
>>+gImageView._ltrAtom = atomSvc.getAtom("ltr");
>>+gFormView._ltrAtom = atomSvc.getAtom("ltr");
>>+gLinkView._ltrAtom = atomSvc.getAtom("ltr");
> File style doesn't go with prefixes (either _ or m) so drop the _s please.
>>- props.AppendElement(gBrokenAtom);
>>+ props.AppendElement(this._brokenAtom);
> Or you could always switch to gBrokenAtom and gLtrAtom ;-)
Now using gBrokenAtom and gLtrAtom!
Pushed to comm-central
http://hg.mozilla.org/comm-central/rev/0f8b5129cfe6
![]() |
Assignee | |
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•