Closed Bug 813892 Opened 12 years ago Closed 12 years ago

Firefox 17 built with old XUL

Categories

(Firefox :: Extension Compatibility, defect, P1)

17 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: georgehdd, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 Build ID: 20121113065533 Steps to reproduce: I have a native extension (C++) for Firefox. I built it today against the latest XUL SDK (17) and it worked flawlessly in FF17 ESR but it didn't work good in FF17 Release. Actual results: Query Interface didn't work good for various web elements like nsIDOMHTMLInputElement . After downloading source code of both Release and ESR builds I noticed that the guids of nsIDOMHTMLInputElement.idl are different: - ESR: e59a4df5-0904-414d-9203-9af2790698ea - RELEASE: 83984fd0-b0b2-11e1-afa6-0800200c9a66 The difference is due to a change which fixed Bug 809865 ( https://bugzilla.mozilla.org/show_bug.cgi?id=809865 ). It seems that the XUL code that the release version of Firefox 17 was built with is different (and older) than the code that the ESR version was built with (and after a little bit of checking it seems to be older than what Beta6 has been built with as well). Expected results: My native extension should have worked in Release version as well. The release version should be built with the new XUL code and a new build should be released as soon as possible.
Severity: normal → blocker
Component: Untriaged → Extension Compatibility
Priority: -- → P1
Summary: Firefox 17 → Firefox 17 built with old XUL
Could the issue be with ESR ? Since the IID change was reverted in change: https://bugzilla.mozilla.org/show_bug.cgi?id=813264 But this change wasn't included in ESR (or XUL SDK 17 for that matter)
Looks like Alex responded to this over in bug 813264 comment 25. 17.0.1esr will pick up the change when it ships. In the mean time, target the 17.0 release.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.