Skip to main content
8 events
when toggle format what by license comment
Nov 8, 2016 at 15:09 comment added Doug Chasman @LucasEnnouchi my comment "simply doing its job: is in direct reference to this sub tread about lightning: namespace issues. That is the challenge when 2 things are conflated in a single thread erroneously. The original post here is an issue in Locker (of course you need to be able to access your own parts of the DOM) and I will have a new bug ID for it shortly.
Nov 8, 2016 at 15:08 comment added Lucas Ennouchi Thank you ! I deleted the link from my answer as it was not relevant.
Nov 8, 2016 at 15:07 history edited Lucas Ennouchi CC BY-SA 3.0
Deleted the link to another case that just brings confusion in this matter.
Nov 8, 2016 at 15:06 comment added Doug Chasman The open bug for the team that owns the lightning: namespace is W-3453049 if you want to reference this in any communications with Salesforce. They are working on it but do not have an ETA yet.
Nov 8, 2016 at 15:02 comment added Lucas Ennouchi Oh okay @Doug. I agree with you my link is not a good example. So what do you mean about "simply doing its job" ? A component cannot access its own DOM elements anymore ? What would be your workaround for this ?
Nov 8, 2016 at 14:54 comment added Doug Chasman Hold on a second Lucas - the post you linked to was about reaching into the internals of a component you do not own (lightning:buttonIcon) that has a design flaw in it that is being corrected. Not the case in the code above. This is not a bug in Locker - it is simply doing its job. The team that owns the lightning: namespace has been alerted, I opened a bug to track it etc and they said it would be fixed by now. Appears to have missed the boat for the current patch. Sigh.
Nov 8, 2016 at 14:47 comment added joshuadelange Ouch! Any ideas when Salesforce will have this fixed?
Nov 8, 2016 at 14:44 history answered Lucas Ennouchi CC BY-SA 3.0