@marcosc At this point, yes. Fixable though. Same in Chromium. @yoavweiss @sgalineau @tobie @DavidBruant @domenic
-
-
Replying to @robinberjon
@robinberjon@yoavweiss@sgalineau@tobie@DavidBruant@domenic I'm told by@bz_moz that it's not fixable. Will need c++ for system access.5 replies 0 retweets 0 likes -
Replying to @marcosc
@marcosc I’d love to hear why.@yoavweiss@sgalineau@tobie@DavidBruant@domenic@bz_moz2 replies 0 retweets 0 likes -
Replying to @robinberjon
@robinberjon@yoavweiss@sgalineau@tobie@DavidBruant@domenic@bz_moz might need to spin up a thread on dev-platform@mozilla1 reply 0 retweets 0 likes -
Replying to @marcosc
@marcosc If Gecko can’t go it, Chromium will just crush it when it works there.@yoavweiss@sgalineau@tobie@DavidBruant@domenic@bz_moz2 replies 0 retweets 0 likes -
Replying to @robinberjon
@robinberjon@marcosc@yoavweiss@sgalineau@tobie@DavidBruant@domenic Call me when Chromium JS can see the page-visible .onclick on nodes2 replies 0 retweets 1 like -
Replying to @really_bz
@bz_moz I haven’t dug into this, but can’t you expose them wrapped? Or am I missing the problem?1 reply 0 retweets 0 likes -
-
Replying to @really_bz
@bz_moz But then I’m not sure which specific problem you’re pointing at so I’m likely grasping at very short straws :)1 reply 0 retweets 0 likes -
Replying to @robinberjon
@robinberjon In blink, privileged JS cannot contain references to unprivileged JS objects. No infrastructure for it.1 reply 0 retweets 0 likes
@robinberjon So e.g. can't get the .response of an unprivileged XHR with an arraybuffer response type and modify the bytes the page sees .
-
-
Replying to @really_bz
@bz_moz Well, JS XPCOM in chrome used to be unable to expose object attributes to content and that changed; one can be optimistic ;)0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.