NPAAPI Plugin - PPAPI Plug-in created by Jeromie Clark in Flash Player Beta Channel - View the full discussionI'm not sure what's up. I may have misunderstood and Chromium-based in practice just means Opera at this point when you're talking about Mac. I'll have to go ask around a little more. Our focus is on Chrome, and Chrome Mac doesn't support the debugger that we're shipping, so it doesn't make a lot of sense to spend energy there until Chrome support is available. Sorry about the confusion though, I use Mac in my day-to-day, but I'm on my Windows machine when I'm debugging with Flash Builder or Flash Pro. PPAPI Debugger works in Opera, I just checked. You do have to go into about:plugins and enable the right one. Other Chromium-based browser may also work, but they have to have added code to look at the default system location for the Pepper plug-in. In the interest of transparency, I don't see us investing a ton of resources here at the moment. I want to respect your time, and if you're just trying to get your day-to-day done without a lot of friction, you're way better off debugging in NPAPI on Mac. We got the PPAPI debugger working to some degree, but it's not really a first-class citizen, mostly because of how ugly it is to try and get it working in the context of PPAPI. We're really dependent on the browser to enable a lot of stuff, and there are much more interesting problems than servicing Flash developers with special APIs and functionality (all of which represent new attack surface to the browser folks). I'm happy to queue up bugs for a rainy day, but the frustration is coming through in your posts and I don't want to give you a false sense that we're going to entirely revamp the debugger in the next few weeks. It's something we'll improve incrementally, but a lot of it is gated by work that would need to be accepted into the Chromium project, or implemented in each browser vendor's individual fork. Controlling the PPAPI debugger through config files is pretty problematic given the complexities around the filesystem isolation in the PPAPI architecture, so it's super clunky in that context. Isolating plug-ins is ultimately a good thing general, and had we built the debugger in 2015, using config files to set all of these flags would probably be a non-starter, but if we were going to complete rebuild how all of that stuff works as a prerequisite to getting an initial PPAPI debugger out the door, odds are that it wouldn't have ever shipped. There's a clear trend in the browser space of restricting filesystem access in general to plug-ins, so we're probably going to have to consider alternate mechanisms eventually, but there are no obvious, easy alternatives jumping out at me. Right now, we have the most freedom in NPAPI, and that's where the debugger plugin is going to work best. If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7314054#7314054 and clicking ‘Correct’ below the answer Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7314054#7314054 To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following" Start a new discussion in Flash Player Beta Channel by email or at Adobe Community For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624. |
1 Correct answer
53
Replies
AdChoices