Reading List 252
- Web Browser Privacy: What Do Browsers Say When They Phone Home? (PDF, 14pp) – “browsers split into three distinct groups from this privacy perspective. In the first (most private) group lies Brave, in the second Chrome, Firefox and Safari and in the third (least private) group lie Edge and Yandex.”
- Google Lighthouse is now available as a Firefox extension
- Why the GOV.UK Design System team changed the input type for numbers – <input type=number> Considered Naughty
- MDN Browser Compatibility Survey – “We know from past surveys that browser compatibility is a very common pain point, and we would like to get a better understanding of these pain points. This survey will take you approximately 10 minutes”
- Why open source matters by the Government Digital Service of Canada
- Things to consider when doing usability testing with disabled people
- How Proactively Publishing Publication Dates Could Help Facebook Fight Fake News – a good idea by Andy Mabbett
- Me! Me! Me! corner: Speaker’s Story: Bruce Lawson, HTML5 Spec Editor and Musician – CFPland interviewed me
- Do NOT click this link! Userinyerface – “a challenging exploration of user interactions and design patterns”. So wonderfully frustrating.
2 Responses to “ Reading List 252 ”
Andrew,
I tried out your extension, and was going to try this bookmarklet, but the highlighter doesn’t work if you highlight over a certain amount of text. The created URL uses a comma to truncate the total quoted text in the query and seems “smart” enough to contextually find the right place to highlight. Do you think you could implement this behavior with your extension?
Regards,
Elena
Hi Bruce! I saw your request on Twitter for a Chrome extension for scroll-to-text-fragment. I know Paul Kinlan made a bookmarklet but I went through the trouble of writing my own extension for it anyways.
Check it out: https://chrome.google.com/webstore/detail/copy-text-fragment-url/bemdbglmlhlkmkgfnleiofphhekephnm
I hope Firefox supports this soon (or rather, everyone comes to the best consensus), if only because Firefox supports the fancy Async Clipboard API in background scripts for extensions, and Chrome doesn’t. This boxed me in to using the @bumble/clipboard library and WebPack… not ideal obviously…
But I was damned if I could be asked to make invisible textareas and do execCommand myself for this one. 😅
Anyways this has already been fairly useful for me, so thank you for the idea!