Menu Search
Jump to the content X X
Smashing Conf Barcelona

You know, we use ad-blockers as well. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf Barcelona, dedicated to smart front-end techniques and design patterns.

Web Development Reading List #172: On Reporting Bugs, DNS Subdomain Takeovers, And Sustainable UX

As web developers, we all approach our work very differently. And even when you take a look at yourself, you’ll notice that the way you do your work does vary all the time. I, for example, have not reported a single bug to a browser vendor in the past year, despite having stumbled over a couple. I was just too lazy to write them up, report them, write a test case and care about follow-up comments.

This week, however, when integrating the Internationalization API for dates and times, I noticed a couple of inconsistencies and specification violations in several browsers, and I reported them. It took me one hour, but now browser vendors can at least fix these bugs. Today, I filed two new issues, because I’ve become more aware again of things that work in one browser but not in others. I think it’s important to change the way we work from time to time. It’s as easy as caring more about the issues we face and reporting them back.

Further Reading on SmashingMag: Link

News Link

  • Web annotations5 are now a web standard6, with a defined data model, vocabulary, and protocol. Let’s hope many of the browser vendors (Microsoft Edge) and service platforms will adopt the standard soon. For us developers it’s a huge opportunity, too, to build standardized annotations that are interoperable and to communicate with each other.
Web Annotation Architecture7
The new Web Annotation standard8 could make conversation happen anywhere on the web and make comment widgets a thing of the past. (Image credit9)

Security Link

Web Performance Link

CSS/Sass Link

Going Beyond… Link

Fix the internet by writing good stuff and being nice to people19
Share and create good content20. A philosophy we all should live by.

And with that, I’ll close for this week. If you like what I write each week, please support me with a donation21 or share this resource with other people. You can learn more about the costs of the project here22. It’s available via email, RSS and online.

— Anselm

Footnotes Link

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
  20. 20
  21. 21
  22. 22

↑ Back to top Tweet itShare on Facebook

is a freelance front-end developer and architect and cares about sustainable front-end experiences and ethical choices in life. He curates the WDRL, a weekly handcrafted web development newsletter that thousands of developers love, subscribe to, and donate for.

  1. 1

    Jeremy Cook

    March 6, 2017 5:39 pm

    Has there been much discussion about the impact of Web Annotations? It seems obvious that this is a social technology with sweeping consequences (good and bad). It is not a benign web technology like `h1` tags.

    For example, do you have to opt-in to Web Annotations? Can a website opt-out? It seems that all websites will be open to annotation. This most definitely is desirable to some, but to all? This opens the door for the online equivalent of graffiti. I see no responsible party. Web annotation services could potentially take responsibility for cleaning the “walls” but what is the incentive to do so? I imagine many online publishers, large and small, would rather not deal these virtual walls, and many more will be completely unaware of what is going on their doorstep. Today, individuals and organizations get to choose if they have a Twitter or Facebook presence, or Disqus comments, but with Web Annotations do the content authors and owners get to choose?

    Here is one article that touches on a commercial web annotation system. Perhaps some similar thoughts but not a direct discussion of W3C Web Annotations.

    Ironically, I haven’t found much discussion of W3C Web Annotations. Maybe I’m not using the right search terms, or maybe the discussion just started.


Leave a Comment

You may use simple HTML to add links or lists to your comment. Also, use <pre><code class="language-*">...</code></pre> to mark up code snippets. We support -js, -markup and -css for comments.

↑ Back to top