Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make it possible to set browsertime.chrome.mobileEmulation.* options
See original GitHub issueCurrently it’s not possible to overwrite the hardcoded deviceName='iPhone 6' (reason is that in analyzeUrl() in plugins/browsertime/analyzer.js chromeIphoneEmulationOptions containing the defaults comes after btOptions.chrome).
Additionally, it’s also not possible to unset the default deviceName, and use other possibly conflicting mobileEmulation options like userAgent (if deviceName and userAgent are both set, then the error 'deviceName' must be used alone appears).
If this was possible, then the current limitation of setting --mobile overriding --browsertime.userAgent could be workarounded.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I released 21.3.0 earlier today that fixes so that --userAgent also will be used for emulated devices.
Hi @barryperez in https://github.com/sitespeedio/browsertime/pull/1688 I’m adding so you can append what you want to the user agent, let me do a follow up in browsertime and also fix so that if you set the --userAgent its automatically set for mobile emulation, then I can fix it in sitespeed.io. Hope to fix it the coming weekend.