Re: Setting property on the element is no longer working on Firefox 45
On Thursday, March 10, 2016 at 2:50:10 PM UTC-5, Kris Maglione wrote: > On Thu, Mar 10, 2016 at 10:44:24AM -0800, Devan Shah wrote: > >This happens in side extension only (works fine on web standalone), i will > >try to extract a simple reproducible scenario. > > > >Is there any way to simulate a extension env on web? > > If your problem is happening in an extension, then filing a bug > and attaching a testcase add-on is your best bet. > > If I had to guess based on what you've told us so far, I'd say > your problem has something to do with X-ray security > wrappers[1]. In general, properties that you add to X-ray > wrappers aren't visible to code running in other globals. I.e., > if you're accessing a web page from an SDK content script, your > view of the DOM nodes are different from the view the web page > sees. This also has implications for properties that you add to > prototypes. > > I don't know of any changes that would have significantly > changed the behavior in 45 vs previous versions, though, so a > testcase would be useful. > > [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/Xray_vision Thanks Kris, I will take a look at Xray_vision and see if I can use it to create a simple reproducible testcase ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thursday, March 10, 2016 at 2:42:14 PM UTC-5, Ted Mielczarek wrote: > On Thu, Mar 10, 2016, at 01:23 PM, Devan Shah wrote: > > hello > > > > When I set a custom property such as element.listofSomething = [] and > > then build the list and add it back to the same element. Then this > > element is passed to a function, now in that function I am no longer to > > access this property that I added to the function. > > > > Was there any sort of changes that would impact this? > > > > Also if I make use of Element.prototype to set a custom variable and try > > to access it for an element it is not available any more. IS there > > something that I am missing. (note this is when inside a plugin) > > FYI, I don't know what your particular bug is, but setting custom > properties on DOM elements is called "expandos", which might help you > file a more useful bug report: > https://developer.mozilla.org/en-US/docs/Glossary/Expando > > -Ted Thanks Ted, I will take a look at this. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thu, Mar 10, 2016 at 10:44:24AM -0800, Devan Shah wrote: This happens in side extension only (works fine on web standalone), i will try to extract a simple reproducible scenario. Is there any way to simulate a extension env on web? If your problem is happening in an extension, then filing a bug and attaching a testcase add-on is your best bet. If I had to guess based on what you've told us so far, I'd say your problem has something to do with X-ray security wrappers[1]. In general, properties that you add to X-ray wrappers aren't visible to code running in other globals. I.e., if you're accessing a web page from an SDK content script, your view of the DOM nodes are different from the view the web page sees. This also has implications for properties that you add to prototypes. I don't know of any changes that would have significantly changed the behavior in 45 vs previous versions, though, so a testcase would be useful. [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/Xray_vision ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thu, Mar 10, 2016, at 01:23 PM, Devan Shah wrote: > hello > > When I set a custom property such as element.listofSomething = [] and > then build the list and add it back to the same element. Then this > element is passed to a function, now in that function I am no longer to > access this property that I added to the function. > > Was there any sort of changes that would impact this? > > Also if I make use of Element.prototype to set a custom variable and try > to access it for an element it is not available any more. IS there > something that I am missing. (note this is when inside a plugin) FYI, I don't know what your particular bug is, but setting custom properties on DOM elements is called "expandos", which might help you file a more useful bug report: https://developer.mozilla.org/en-US/docs/Glossary/Expando -Ted ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On 2016-03-10 1:44 PM, Devan Shah wrote: This happens in side extension only (works fine on web standalone), i will try to extract a simple reproducible scenario. Is there any way to simulate a extension env on web? Thanks I do not believe so. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
Devan, I did a quick search and it looks like you'd be a new bugzilla contributor, so thank you! These have not been edited in a while, but if you're looking for guidance on writing a bug https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines (nudge to the community, have a look at this and update it!) The things that would be most helpful are * reproduction steps * isolated example Thanks, -- Emma Humphries, Bugmaster On Thu, Mar 10, 2016 at 10:23 AM, Devan Shah wrote: > hello > > When I set a custom property such as element.listofSomething = [] and then > build the list and add it back to the same element. Then this element is > passed to a function, now in that function I am no longer to access this > property that I added to the function. > > Was there any sort of changes that would impact this? > > Also if I make use of Element.prototype to set a custom variable and try > to access it for an element it is not available any more. IS there > something that I am missing. (note this is when inside a plugin) > > Thanks > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thursday, March 10, 2016 at 1:32:41 PM UTC-5, Josh Matthews wrote: > Hi Devan! This is an interesting bug report, but it's lacking some > useful information to help triage it. Does this problem occur in a web > page, or extension, or some other environment? Can you create a minimal > example of the issue that anyone else could use to reproduce the problem > you're observing? > > Cheers, > Josh > > On 2016-03-10 1:23 PM, Devan Shah wrote: > > hello > > > > When I set a custom property such as element.listofSomething = [] and then > > build the list and add it back to the same element. Then this element is > > passed to a function, now in that function I am no longer to access this > > property that I added to the function. > > > > Was there any sort of changes that would impact this? > > > > Also if I make use of Element.prototype to set a custom variable and try to > > access it for an element it is not available any more. IS there something > > that I am missing. (note this is when inside a plugin) > > > > Thanks > > This happens in side extension only (works fine on web standalone), i will try to extract a simple reproducible scenario. Is there any way to simulate a extension env on web? Thanks ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
Hi Devan! This is an interesting bug report, but it's lacking some useful information to help triage it. Does this problem occur in a web page, or extension, or some other environment? Can you create a minimal example of the issue that anyone else could use to reproduce the problem you're observing? Cheers, Josh On 2016-03-10 1:23 PM, Devan Shah wrote: hello When I set a custom property such as element.listofSomething = [] and then build the list and add it back to the same element. Then this element is passed to a function, now in that function I am no longer to access this property that I added to the function. Was there any sort of changes that would impact this? Also if I make use of Element.prototype to set a custom variable and try to access it for an element it is not available any more. IS there something that I am missing. (note this is when inside a plugin) Thanks ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Setting property on the element is no longer working on Firefox 45
hello When I set a custom property such as element.listofSomething = [] and then build the list and add it back to the same element. Then this element is passed to a function, now in that function I am no longer to access this property that I added to the function. Was there any sort of changes that would impact this? Also if I make use of Element.prototype to set a custom variable and try to access it for an element it is not available any more. IS there something that I am missing. (note this is when inside a plugin) Thanks ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform