Diigo Bookmarks 05/04/2019

2019年5月4日 著

• Implementing a Mockup: CSS Layout Step by Step

  "If your usual strategy is to approach layout in an item-by-item way - put A over here, and now that A is in its place, I want to put B over there... well, that's a guaranteed route to frustration. CSS doesn't work like Sketch or Photoshop."

• Making the Move from jQuery to Vue | CSS-Tricks

  "The Vue application is a bit more verbose, but note how the markup has a direct connection between the action ("click") and the function that will be called. Vue's code doesn't have a tie back to the DOM (outside of the el portion where we define where it needs to work). This was easily one of the things that sold me on Vue the most -- it feels easier to tell what is going on."

• A Book Apart, Progressive Web Apps

  "Jason Grigsby answers the what, why, and how of progressive web apps, from making the case in your organization to reaching your users in bold, new ways. Build your audience, increase revenue, and widen the web's reach--all with the power of progressive web apps."

• A Conspiracy To Kill IE6

  "The bittersweet consequence of YouTube's incredible growth is that so many stories will be lost underneath all of the layers of new paint. This is why I wanted to tell the story of how, ten years ago, a small team of web developers conspired to kill IE6 from inside YouTube and got away with it."

• WPCampus releases results of the Gutenberg accessibility audit - WPCampus: Where WordPress Meets Higher Education

  "In late 2018, WPCampus released a request for proposals to conduct an accessibility audit of the WordPress block editor, also known as Gutenberg. In early 2019, we announced our selection of Tenon, LLC to conduct the audit, at a cost of $31,200."

• Digging Into The Display Property: Box Generation -- Smashing Magazine

  "For this reason, it took many of us by surprise to realize that display: contents was, in fact, removing the element from the accessibility tree in the two browsers (Chrome and Firefox) that had implemented it. Therefore changing the document semantics, making it so that a screen reader did not know that a list was a list once the ul had been removed using display: contents. This is a browser bug -- and a serious one at that."