CSS and Its Little Background
The fourth edition of the book, completed in mid-2017, does its best to reflect the state of CSS at the time. We assume that anything that touches on detail is either already widely supported by browsers at writing or will be released shortly after.
Therefore, CSS features that are still in development or known to be declining in support are not discussed here. Instead, I hope this article will provide a more detailed understanding of how they work when they are needed in certain situations, such as the back end.
With each new release, there’s an optional section detailing similar situations where things went wrong because they were really out of my range. Still, it’s not always public before release: This article seems to cover all types of issues — considering what today’s browsers might need, This article is worth a look — especially since most developers don’t realize it yet.
CSS and Documents
Now, this article might not seem important because I didn’t look at how all these tools were originally developed? No, we’ve been exploring this for months, even years. It’s a waste of time. This article explores an interesting feature of Web browsers in new versions: those from the first version are no longer supported. This is a very controversial thing, especially since most developers don’t know what “support” means until Google announces something useful within a few hours…. So far, there are two popular ways to define version-based support; So which one should Chrome follow?