In this article we review some of the most useful ones. But there are much more efficient ways to test across browsers, using either free or commercial Web services and software. That was fine if you had access to a bunch of different computers (and had some time to kill). The old-school way to test code was to load your website on as many computers as you could find, using as many different combinations of browsers and operating systems as possible. But because that day is still a way off (if it will really come at all), testing your design the advanced browsers as well as legacy browsers is a necessary part of any project. Find a tool that fits your workflow with a little help from Cameron Chapman.Īt some point in the future, the way that all major browsers render Web code will likely be standardized, which will make testing across multiple browsers no longer necessary as long as the website is coded according to Web standards. I'm genuinely tempted to find the time to make a PR.Regardless of the tool you choose, testing early and often during the Web development process can save you from a lot of headaches later. That would have no impact on users, but would push web developers to fix their slow pages. Chrome should display a blank screen when a website falls below 60fps when devtools is open. Websites would get a lot faster pretty quickly if Chrome did that.)ĮDIT: Actually. Browsers could just display a blank screen whenever a web site falls below 60fps. ![]() (I can actually think of an alternative solution that browser vendors could do. If we want a faster web we need to get web devs to test on slower browsers and more realistic target devices. Essentially, web pages will always expand to fill the available resources of the dev's machine and if you use their code on a less powerful computer you're out of luck. Increasing the speed of the browser just means web devs will accept that code is fast enough when they use it, regardless of whether or not its fast enough when a user on a less powerful machine uses it. Developers will build and test (or not test) things on their powerful Macbooks, and usually ship things that aren't noticeably slow for them, then a user with a $300 Windows laptop from Walmart will struggle to click on things. This is a bit off topic I guess, but I don't think the goal of fixing a slow Web can be achieved by building a faster Web browser. This would be great to clean up all the old tabs that accumulate. Or maybe you find a clever UI to select and close all old, not recently used tabs. Or you could move all tabs with "office" to a new window. Then press "hacker" and it highlights all tabs with hacker(news), and ⌘-w to close them. This is the one feature for which I could imagine buying a pro version.Īnother thing that I think would be cool is a tab filter. In any case, if your extension model is powerful enough, somebody could write an open source extension to do it). It would be really great if you could implement Firefox sync (the source is available, I'm not sure if there are license problems in using it from a third party browser. One thing that is really important to me is bookmark sync. ![]() The killer feature is the support of WebExtensions (ad blocker!) So I like the idea of a better version of Safari. I kinda like Safari, although it has weird bugs (e.g.: if you use tab groups, it will randomly navigate back and forth). I just got a new MacBook after using Windows, and am trying to do things the "Mac" way, before I attempt to customize it too much.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |