1
edit
NPAPI:VisibilityNotification: Difference between revisions
Jump to navigation
Jump to search
m
typo
m (→Alternatives) |
m (typo) |
||
| Line 27: | Line 27: | ||
There has been suggested that every plugin that would need such service would have to find its own way to implement it but this seems unnecessary as there is architecturally clean way to do this. | There has been suggested that every plugin that would need such service would have to find its own way to implement it but this seems unnecessary as there is architecturally clean way to do this. | ||
For example if there is a web page that has 5 plugin instances, each using 20% of CPU. Any user interaction will be sluggish. However if these instances are located so that only one of them can be visible, and if visibility information is used to pause invisible plugins, then the CPU usage would be 20%. This would improve the browsing | For example if there is a web page that has 5 plugin instances, each using 20% of CPU. Any user interaction will be sluggish. However if these instances are located so that only one of them can be visible, and if visibility information is used to pause invisible plugins, then the CPU usage would be 20%. This would improve the browsing experience a lot. Because of the small displays and weak CPU that are typically used on mobile devices this is realistic example. | ||
= Specification = | = Specification = | ||