Closed Bug 813264 Opened 7 years ago Closed 7 years ago

Bug 809865 or Bug 810726 broke Skype click-to-call

Categories

(Core :: General, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla17
Tracking Status
firefox17 + fixed
firefox18 --- unaffected
firefox19 --- unaffected
firefox-esr17 18+ fixed

People

(Reporter: akeybl, Assigned: johns)

Details

(Whiteboard: [qa:pending compatible addon])

Attachments

(2 files, 4 obsolete files)

We've received email from Skype that 

"Rama Kurvakat who is a developer in Click-to-call team informed me today that there have been incompatible changes in the API in FF 17 beta 6. These changes in b6 which essentially invalidated all our testing effort on b5."
In email, Benjamin got this down to one of two bugs:

https://hg.mozilla.org/releases/mozilla-beta/rev/b53dbef72a55
Bug 809865 - Disable inputmode. r=smaug a=lsblackk 

https://hg.mozilla.org/releases/mozilla-beta/rev/74d121044a74
Bug 810726: Backout 34d30fa24371 for infinite loop problems. [r=roc][a=lsblakk] 

We need to determine which of these two is the issue, come up with a patch, and consider re-spinning.
Marcia is looking into this right now.
QA Contact: mozillamarcia.knous
Johns is writing a patch to undo the two IID changes.
Assignee: nobody → jschoenick
Attachment #683284 - Flags: review?(benjamin)
Attachment #683285 - Flags: review?(benjamin)
Comment on attachment 683284 [details] [diff] [review]
Restore inputmode attribute to nsIDOMHTMLElement as [noscript] to avoid IID change

Please add a brief comment referencing this bug explaining that this is for binary compat.
Attachment #683284 - Flags: review?(benjamin) → review+
Attachment #683285 - Flags: review?(benjamin) → review+
Product: Firefox → Core
We are testing in a VM now - I tested on different hardware and was not able to get it work even using FF 16.0.2,
Attachment #683289 - Flags: approval-mozilla-release+
Attachment #683290 - Flags: approval-mozilla-release+
The extension is not compatible with earlier versions (Fxbeta 4 or even beta 1).
(In reply to juan becerra [:juanb] from comment #10)
> The extension is not compatible with earlier versions (Fxbeta 4 or even beta
> 1).

Firefox 17b4 or b1.
I finally got it work in a Win XP VM in 16.0.2, but when trying to move to Firefox 17b5 it is not installing the extension.

As Juan notes, it isn't compatible when you install it in Firefox 17, so it makes it difficult to test the breakage they are citing between B5 and B6.
(In reply to Marcia Knous [:marcia] from comment #12)
> I finally got it work in a Win XP VM in 16.0.2, but when trying to move to
> Firefox 17b5 it is not installing the extension.
> 
> As Juan notes, it isn't compatible when you install it in Firefox 17, so it
> makes it difficult to test the breakage they are citing between B5 and B6.

Thanks for testing. Even still, let's move forward with the respin since Skype won't push out a newer update for a week (thus making click-to-call non-functional on FF17) and we suspect that other binary add-ons may be affected (Yandex/Bandoo instability, for instance).
Comment on attachment 683312 [details] [diff] [review]
Restore MozColumnFill attribute to nsIDOMCSS2Properties as [noscript] to avoid IID change

r=dbaron (though I'd like bz to look at this as well when he gets back from dinner)

Given that bug 753517 is in Firefox 17, I'm not too worried about what these methods do.
Attachment #683312 - Flags: review+
Attachment #683312 - Flags: feedback?(bzbarsky)
Comment on attachment 683312 [details] [diff] [review]
Restore MozColumnFill attribute to nsIDOMCSS2Properties as [noscript] to avoid IID change

[Triage Comment]
BZ won't be back for a few hours and we need to go to build to hit our Tuesday ship. Let's land on mozilla-release.
Attachment #683312 - Flags: approval-mozilla-release+
Attachment #683311 - Flags: approval-mozilla-release+
Attachment #683312 - Flags: checkin+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Can someone theorize a list of add-ons for QA to test overnight?
Comment on attachment 683312 [details] [diff] [review]
Restore MozColumnFill attribute to nsIDOMCSS2Properties as [noscript] to avoid IID change

Given that these properties are not declared pure virtual, this looks lovely!
Attachment #683312 - Flags: feedback?(bzbarsky) → feedback+
Duplicate of this bug: 813568
I manually verified that inputelement.inputmode is undefined in 17.0build2.
(In reply to John Schoenick [:johns] from comment #18)
> Comment on attachment 683311 [details] [diff] [review]
> Restore inputmode attribute to nsIDOMHTMLElement as [noscript] to avoid IID
> change
> 
> https://hg.mozilla.org/releases/mozilla-release/rev/8cdcad2877b9
> https://hg.mozilla.org/releases/mozilla-release/rev/fe2f81698ee1

Why hasn't this been committed to ESR as well ?
(In reply to georgehdd from comment #23)
> (In reply to John Schoenick [:johns] from comment #18)
> > Comment on attachment 683311 [details] [diff] [review]
> > Restore inputmode attribute to nsIDOMHTMLElement as [noscript] to avoid IID
> > change
> > 
> > https://hg.mozilla.org/releases/mozilla-release/rev/8cdcad2877b9
> > https://hg.mozilla.org/releases/mozilla-release/rev/fe2f81698ee1
> 
> Why hasn't this been committed to ESR as well ?

or XUL SDK 17 ? (xulrunner-17.0.en-US.win32.sdk)
(In reply to georgehdd from comment #23)
> (In reply to John Schoenick [:johns] from comment #18)
> > Comment on attachment 683311 [details] [diff] [review]
> > Restore inputmode attribute to nsIDOMHTMLElement as [noscript] to avoid IID
> > change
> > 
> > https://hg.mozilla.org/releases/mozilla-release/rev/8cdcad2877b9
> > https://hg.mozilla.org/releases/mozilla-release/rev/fe2f81698ee1
> 
> Why hasn't this been committed to ESR as well ?

We're going to be pushing this out as part of our next ESR release, 17.0.1esr. ESR17 usage will be very low this cycle, given the qualification period necessary by most major deployments. Please target FF17.0 mainline for the time being.
Comment on attachment 683311 [details] [diff] [review]
Restore inputmode attribute to nsIDOMHTMLElement as [noscript] to avoid IID change

[Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration:
Syncs IIDs with 17 release

User impact if declined:
Potential addon incompatibilities between 17 and 17ESR

Fix Landed on Version:
17

Risk to taking this patch (and alternatives if risky): 
Changes IIDs from what was on 17.0.0esr

String or UUID changes made by this patch: 
nsHTMLInputElement nsIDOMCSS2Properties
Attachment #683311 - Flags: approval-mozilla-esr17?
Attachment #683312 - Flags: approval-mozilla-esr17?
Comment on attachment 683311 [details] [diff] [review]
Restore inputmode attribute to nsIDOMHTMLElement as [noscript] to avoid IID change

We're going to release a 17.0.1 (both normal and ESR) so please go ahead with landing this to the mozilla-esr17 branch asap.
Attachment #683311 - Flags: approval-mozilla-esr17? → approval-mozilla-esr17+
Attachment #683312 - Flags: approval-mozilla-esr17? → approval-mozilla-esr17+
(In reply to John Schoenick [:johns] from comment #28)
> https://hg.mozilla.org/releases/mozilla-esr17/rev/30328bbb0901
> https://hg.mozilla.org/releases/mozilla-esr17/rev/016290a598e0

John, sorry for not mentioning it earlier - can you please land this to the ESR17 relbranch as well? There have been some security landings to mozilla-esr17 default that we are not intending to ship in respin.

GECKO170_2012111914_RELBRANCH
Do we have a compatible version of Skype to test this with?
The version of Skype Click-to-Call found here http://www.skype.com/intl/en/get-skype/on-your-computer/click-to-call/windows/ still doesn't work on Firefox 17.0.1 (Build ID: 20121128204232): the phone numbers aren't highlighted and can't be phoned.

It doesn't work on Chrome either.
(In reply to Manuela Muntean from comment #32)
> The version of Skype Click-to-Call found here
> http://www.skype.com/intl/en/get-skype/on-your-computer/click-to-call/
> windows/ still doesn't work on Firefox 17.0.1 (Build ID: 20121128204232):
> the phone numbers aren't highlighted and can't be phoned.
> 
> It doesn't work on Chrome either.

I cannot install Skype CTC at all on FF 17.0.1 on Win XP and Win 8.
(In reply to Manuela Muntean from comment #32)
> The version of Skype Click-to-Call found here
> http://www.skype.com/intl/en/get-skype/on-your-computer/click-to-call/
> windows/ still doesn't work on Firefox 17.0.1 (Build ID: 20121128204232):
> the phone numbers aren't highlighted and can't be phoned.
> 
> It doesn't work on Chrome either.

I forgot to mention that I've tested on Windows 7 32-bit.
(In reply to Paul Silaghi [QA] from comment #33)
> I cannot install Skype CTC at all on FF 17.0.1 on Win XP and Win 8.

When starting the installer here [http://www.skype.com/intl/en/get-skype/on-your-computer/click-to-call/windows/], on the specified OSs, the installation process goes to the end without giving any errors. Yet, when starting Chrome and Firefox, the add-on shows up on Chrome but it doesn't appear anywhere for Firefox (not in Extensions folders, Add-ons Manager etc).
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #31)
> Do we have a compatible version of Skype to test this with?

We have not received a newer version from Skype. As long as 17.0.1 is behaving no differently than 17.0, we'll be in good shape for when Skype does release their latest version.
(In reply to Alex Keybl [:akeybl] from comment #36)
> (In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #31)
> > Do we have a compatible version of Skype to test this with?
> 
> We have not received a newer version from Skype. As long as 17.0.1 is
> behaving no differently than 17.0, we'll be in good shape for when Skype
> does release their latest version.

Okay, we've at least confirmed that. I'm dropping this from the 17.0.1 test plans to remove confusion. We'll still track for verification once we have a compatible version to test.
Keywords: verifyme
Whiteboard: [qa:pending compatible addon]
mass remove verifyme requests greater than 4 months old
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.