"Chrome-Only CSS" ... not so

[WebMechanic]

I presume you're aware that several "Chrome-Only CSS" hacks also turn red in EdgeHTML and Firefox. For EdgeHTML # 3, 4, 5, 10, 12, 17, 18, 19, 25, 26, 27, 31, 35, 36, 39, 48, 49, 52, 56 For recent Firefox # 10, 12, 19, 20, 21, 23, 25, 27, 31, 33, 35, 39, 42, 44, 46, 49, 52, 54, 56.

Numbers from adding this to the current live page:

h2 {counter-reset:hakk}
.styled_block {counter-increment:hakk}
.styled_block::after {
  z-index:27;
  position:absolute;
  font-size:smaller;
  content:counter(hakk);
  margin-top:-1em;
  height:1em;
}

[browserstrangeness]

Not surprising. I appreciate the list. When they decide to add a webkit addition to a browser it 'wakes up' many that were not compatible before. They didn't do that in older versions of course. I recently finished documenting the firefox and safari ones, but am looking at. I intend to document the changes, but it is exhausting testing all of them ;)

[WebMechanic]

but it is exhausting testing all of them ;)

I bet it is, but you're doing a great job as the Curator of Strageness™

I guess FF 44-57/59 will be bugging you a lot, that's when they (and M$) began to accept webkit aliases and finally ended faking it with their Quantum release. I don't think they add new prefixed properties anymore; this path almost broke the web and gave us the mess we ourselves have caused using all this fancy experimental eye candy Google and Apple provided.

[browserstrangeness]

Thank you for the compliment most definitely. The aliases do give us a bunch of options to develop these types of things in the first place. So bugging me isn't really all that true. Locating which versions serve these options up is like a treasure hunt, even though it can take time.