I think we should do that, specially as the UI part will likely involve some strings, which cannot slip past the uplift on Monday. I could keep the UI part but if someone else works in parallel on the other part it will help unblock some of this work on the ongoing API changes for the plugin.
----- Original Message ----- From: "Benjamin Smedberg" <[email protected]> To: [email protected], "Felipe Gomes" <[email protected]> Cc: "Georg Fritzsche" <[email protected]> Sent: Tuesday, July 15, 2014 5:19:37 PM Subject: GMP crash reporting update (schedule slip likely) The bug for hooking up crash reporting for GMP plugins is likely to slip past this week, and I'd like to talk about how to reduce risk there. Part of the problem is that I may not have broken that bug down sufficiently. There's really two parts to the problem: associating a GMP crash with one or more DOM windows, and then hooking up the UI. It's not hard to find peple on fx-team to take care of the UI hookup, but the other part is hard. It's still not clear to me how to do that, or whether the answer differs in the case of a webrtc-GMP and a video-decoder-GMP. In any case, I'd like to kick of a discussion about this work, especially since we're right up against 33 branch, and Felipe is fully booked and going on vacation later next week. Perhaps we should immediately break this down into the two bugs and somebody from the media team can help with the GMP->domwindow hookup? --BDS _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
