User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5 Steps to reproduce: In my add-on, i use custom events to communicate beetween sidebars and the browser main window. A custom event is throwed to the main window when the sidebar is opened, like there : https://github.com/nfroidure/BBComposer/blob/ebd770615095e71efaa9eca73fbafe3bd16475e0/chrome/bbcomposer/content/sidebar/style.js#L12 As you can see, i set a sidebarName property, allowing me to know what sidebar is opened. The code that receive this event in the main window is there : https://github.com/nfroidure/BBComposer/blob/ebd770615095e71efaa9eca73fbafe3bd16475e0/chrome/bbcomposer/content/bbcManager.js#L92 The test case is : 1- Install the current dev add-on source code 2- Right click on a textarea 3- Try to open a sidebar 4- Look at the message printed in the error console Actual results: The custom event hasn't the sidebarName property when it is received (tested on 15 & 16.0a). It print : Ewk: Sidebar load event: Did not find the property hEvent.sidebarName Expected results: On Firefox release channel (v12 & v13) : It prints the right message, indicating that the custom event sidebarName property is well retrieved : Ewk: Sidebar load event: css
I confirm this bug, on Linux x86_64 and Mac. Is it a wanted restriction? I'm using custom events in my extensions/xulrunner apps, so it's very useful to set a custom "data" property. I also tried to add properties in the "detail" object, but they are also removed...
Hi, I would like to have more informations on this bug. Is it really a bug or did you remove the ability to attach datas to the custom event throwed between the sidebar and the chrome context ? It's very important for me to know if i have to wait this bug to be fixed or if i should update my add-ons cause the described behavior of this bug is now into the release channel and some of my extensions are now bugged. Thanks in advance
Component: Untriaged → Extension Compatibility
OS: Linux → All
Hardware: x86_64 → All
Jorge: I can't find information on this being deprecated. Do you know how we could find that out?
Mass-closing old Extension Compatibility bugs that relate to legacy add-ons or NPAPI plug-ins. If you think this bug is still valid, please reopen or comment. Sorry for the bug spam, and happy Friday!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.