This would be amazing. I highly support this suggestion!On Nov 26, 2014 11:16 AM, "Florian Bösch" <firstname.lastname@example.org> wrote:Well, you'd want to quickly change it for development. Not as a standard, more like, a quick way to do it just for one page (the one you've got the dev tools open), without all other tabs going haywire.On Wed, Nov 26, 2014 at 7:58 PM, Kenneth Russell <email@example.com> wrote:This can be done in Chrome by launching it with the command line
argument --disable-gpu-vsync. Is it worth standardizing this?
On Wed, Nov 26, 2014 at 9:49 AM, Florian Bösch <firstname.lastname@example.org> wrote:
> It occurred to me that it'd be useful to have a way to disable the 60fps
> limit like you would disable network caching or stuff like that in the dev
> tools per checkbox.
> Would this at all be feasible for browser vendors?