(In reply to Alastor Wu [:alwu] from comment #16) > Per [4], websites have ways to detect if a user is in a PB or not. There's no standardized way for that, and any trial includes hacky way to check whether a given API doesn't work (that is known to be broken only in PBM, just like in this bug). So > So if watching DRM playback causes the device limitation which seems the website's responsibility to handle the issue. So I don't think this is true. We don't want websites to handle PBM and are trying hard to make things seamless as possible in PBM.
Bug 1706121 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Alastor Wu [:alwu] from comment #16) > Per [4], websites have ways to detect if a user is in a PB or not. There's no standardized way for that, and any trial includes hacky way to check whether a given API doesn't work (that is known to be broken only in PBM, just like in this bug). So, > So if watching DRM playback causes the device limitation which seems the website's responsibility to handle the issue. I don't think this is true. We don't want websites to handle PBM and are trying hard to make things seamless as possible in PBM.
(In reply to Alastor Wu [:alwu] from comment #16) > Per [4], websites have ways to detect if a user is in a PB or not. AFAIK there's no standardized way for that, and any trial includes hacky way to check whether a given API doesn't work (that is known to be broken only in PBM, just like in this bug). So, > So if watching DRM playback causes the device limitation which seems the website's responsibility to handle the issue. I don't think this is true. We don't want websites to handle PBM and are trying hard to make things seamless as possible in PBM.