Test pilot notifications have broken / transparent UI in Thunderbird

RESOLVED FIXED in Thunderbird 14.0

Status

Thunderbird
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: dholbert, Assigned: standard8)

Tracking

13 Branch
Thunderbird 14.0
Dependency tree / graph

Thunderbird Tracking Flags

(thunderbird12- fixed, thunderbird13+ fixed)

Details

(URL)

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

5 years ago
Created attachment 587722 [details]
screenshot

Today I got a test pilot notification for "A Week in the Life of a Mail Client" over my Thunderbird Daily session.

This popup was partly translucent and near-impossible to read.  Looks pretty horked.  Filing this bug on that.

System info:
 - 32-bit Ubuntu 11.04 (with the default "Unity" desktop).
 - Up-to-date Thunderbird Daily:
    Mozilla/5.0 (X11; Linux i686; rv:12.0a1) Gecko/20120111 Thunderbird/12.0a1
 - Test Pilot for Thunderbird 1.3.4  (bundled I believe; I don't recall explicitly installing it)

(Also, FWIW, I've been running Thunderbird Daily for months, and this is the first Test Pilot notification I've ever gotten there IIRC.)
(Assignee)

Updated

5 years ago
Component: Test Pilot → General
Product: Mozilla Labs → Thunderbird
QA Contact: test-pilot → general
(Assignee)

Updated

5 years ago
Blocks: 729127
OS: Linux → All
Hardware: x86 → All
I'm also seeing this on EarlyBird (TB 12).
This problem does not seem to occur on beta (TB 11).
Steps for diagnosis:

1)  Open up the preferences dialog, and change the mailnews.start_page.override_url to equal chrome://testpilot/content/debug.html
2)  Close the preferences dialog
3)  Go to Help > What's New
4)  In the diagnostic tab that appears, click on "Show Dummy Popup"
(Assignee)

Comment 4

5 years ago
From testing on Mac, I can confirm this isn't happening in TB 11 beta.
Assignee: nobody → nisses.mail
tracking-thunderbird12: --- → +
Version: unspecified → 12
(Reporter)

Comment 5

5 years ago
Confirmed that Comment 3 repro's the problem for me in EarlyBird 12 from yesterday (20120228)
The latest EarlyBird no longer has this issue.

I suspect this is due to the fact that bug 497995 was backed out of mozilla-aurora (which also explains the weird boxes we're currently seeing in the tab selector - being addressed in bug 713852).

So, for the person investigating this - I would investigate how bug 497995 changes the behaviour of border-image.
(Assignee)

Comment 7

5 years ago
Updating flags per comment 6
status-thunderbird12: --- → unaffected
tracking-thunderbird12: + → -
tracking-thunderbird13: --- → +
(Assignee)

Updated

5 years ago
Blocks: 497995
(Assignee)

Comment 8

5 years ago
Created attachment 607123 [details] [diff] [review]
The fix

Well spotted Mike! Here's the fix ported from bug 497995 and attachment 554137 [details] [diff] [review]. I've tested it on Mac on beta, earlybird & trunk and seems fine.

Note: the old lines are left in to support the versions where bug 497995 doesn't apply.
Assignee: nisses.mail → mbanner
Status: NEW → ASSIGNED
Attachment #607123 - Flags: review?(mconley)
(Assignee)

Updated

5 years ago
Version: 12 → 13
Comment on attachment 607123 [details] [diff] [review]
The fix

Review of attachment 607123 [details] [diff] [review]:
-----------------------------------------------------------------

Hm... I'm a little amazed that this will do the right thing when displayed in older versions of TB...aren't CSS styles applied in order, such that the second -moz-border-image will override the first?

::: mail/app/profile/extensions/tbtestpilot@labs.mozilla.com/content/browser.css
@@ +76,4 @@
>   -moz-border-image: url(chrome://testpilot-os/skin/notification-tail-up.png) 26 56 22 18 / 26px 56px 22px 18px round stretch;
> + // Supported in Gecko >= 13
> + -moz-border-image: url(chrome://testpilot-os/skin/notification-tail-up.png) 26 \
> +50 22 18 fill repeat;

If we're going to break up the long line like this, I'd rather the "50 22 18 fill repeat;" be aligned so that it starts beneath the "u" in "url(chrome://..."

Also, I'm curious - why was that line broken up, but not the one on line 93?
(Assignee)

Comment 10

5 years ago
(In reply to Mike Conley (:mconley) from comment #9)
> Comment on attachment 607123 [details] [diff] [review]
> The fix
> 
> Review of attachment 607123 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> Hm... I'm a little amazed that this will do the right thing when displayed
> in older versions of TB...aren't CSS styles applied in order, such that the
> second -moz-border-image will override the first?

When I tested it on an older one, it seemed that the line with "fill" now added was rejected as it didn't conform to spec. The same happened the opposite way around.


> >   -moz-border-image: url(chrome://testpilot-os/skin/notification-tail-up.png) 26 56 22 18 / 26px 56px 22px 18px round stretch;
> > + // Supported in Gecko >= 13
> > + -moz-border-image: url(chrome://testpilot-os/skin/notification-tail-up.png) 26 \
> > +50 22 18 fill repeat;
> 
> If we're going to break up the long line like this, I'd rather the "50 22 18
> fill repeat;" be aligned so that it starts beneath the "u" in
> "url(chrome://..."
> 
> Also, I'm curious - why was that line broken up, but not the one on line 93?

Oops, that was just a copy and paste from emacs in bash terminal error - they weren't intended to be wrapped.
(Assignee)

Comment 11

5 years ago
Created attachment 607522 [details] [diff] [review]
The fix v2

Correct version per comments.
Attachment #607123 - Attachment is obsolete: true
Attachment #607123 - Flags: review?(mconley)
Attachment #607522 - Flags: review?(mconley)
Comment on attachment 607522 [details] [diff] [review]
The fix v2

Review of attachment 607522 [details] [diff] [review]:
-----------------------------------------------------------------

The fact that it degrades gracefully is rather surprising, but still pleasant. :)

This looks good to me.  Thanks for your work!
Attachment #607522 - Flags: review?(mconley) → review+
(Assignee)

Comment 13

5 years ago
Checked in:

http://hg.mozilla.org/comm-central/rev/ffb738522343
http://hg.mozilla.org/comm-central/rev/fb3b7c4c409e
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 14.0
(Assignee)

Comment 14

5 years ago
Comment on attachment 607522 [details] [diff] [review]
The fix v2

[Triage Comment]
Although AMO will provide the latest version, I want to push this out to all branches, so that users installing fresh will get the new version straight off.
Attachment #607522 - Flags: approval-comm-beta+
Attachment #607522 - Flags: approval-comm-aurora+
(Assignee)

Comment 15

5 years ago
(In reply to Mark Banner (:standard8) from comment #13)
> Checked in:
> 
> http://hg.mozilla.org/comm-central/rev/ffb738522343
> http://hg.mozilla.org/comm-central/rev/fb3b7c4c409e

Oh the latter of these was for a version bump for test pilot so that we can push this fixed version to AMO.
(Assignee)

Comment 16

5 years ago
Checked in:

http://hg.mozilla.org/releases/comm-aurora/rev/394d81db3262
http://hg.mozilla.org/releases/comm-aurora/rev/a42983902c5d
http://hg.mozilla.org/releases/comm-beta/rev/45159577008d
http://hg.mozilla.org/releases/comm-beta/rev/5c92b414af33
status-thunderbird12: unaffected → fixed
status-thunderbird13: --- → fixed
This appears to be an issue again on comm-central.  Screenshot forthcoming...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Created attachment 609403 [details]
Transparent TestPilot UI on comm-central

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120326 Thunderbird/14.0a1

TestPilot 1.3.8 on Windows 7.  Might affect the other platforms too.
Mark any idea why this came back ?
Status: REOPENED → NEW
(Assignee)

Comment 20

5 years ago
I did originally fix it locally, however, it appears that adding the wrong style of comments before I posted the patch broke it again. I thought I had re-tested it before I pushed it to AMO etc, however, somewhere along the line my testing broke down :-(

The good news is that bug 738052 has already fixed this in-tree. So we can get a new version of it out easily.
Status: NEW → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.