Meh.
This works in Firefox:
Show HN: CSS Pokemon – created with clip-path and CSS variables
21–30 of 45 posts
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#22Edit: Major correction: it appears Firefox only supports clip-path behind a flag. Enabling this flag makes the experiment appear in Firefox. --- It's Webkit/Blink-only - no support for other browsers. It says it uses clip-path and variables, both supported in Firefox, so I see no compelling reason for this. Also viewing it in Chrome, I don't see anything that would actually require the use of clip-path or variables -…
Unfortunately Firefox only supports clip-path behind a flag.
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#23Edit: Major correction: it appears Firefox only supports clip-path behind a flag. Enabling this flag makes the experiment appear in Firefox. --- It's Webkit/Blink-only - no support for other browsers. It says it uses clip-path and variables, both supported in Firefox, so I see no compelling reason for this. Also viewing it in Chrome, I don't see anything that would actually require the use of clip-path or variables -…
It seems to me that nowadays Webkit/Blink has replaced IE for developers not caring about interoperability – with some even going so far as to claim „IE? but nobody uses that!“.
Eh, it always only seems to be the case for experiments. Stuff that has no use case besides "looking fun" and probably being a fun challenge to work at. There are a few FF only, and many that are Chrome only.
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#24I made another pokemon in CSS (view from behind): https://jsfiddle.net/t2mngvwn/show/
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#25Earlier quoted context omitted.
Chrome is closed-source (though based on the open-source Chromium project so it can nicely claim the associated kudos of an open-source project). IE also "improved" rapidly back in the IE4/5/6 days, adding features such as CSS filters and AJAX. These "improvements" were considered much needed progress by developers at the time; later, with the wisdom of hindsight, rightly seen as proprietary extensions with little to…
IE 6 did not improve for many years (7?) until Firefox got them to do IE7- also comparing the parts of chrome to the parts of IE6.... I'm not sure I buy your quick dismal of the open source difference between the two engines. I can download and compile chromium which is almost identical to chrome. What equivalent did we have with IE from 2000 until today I still can't download IE and compile from source?
In terms of improvement, I was referring to IE4->IE5->IE6
I'm not really sure what you mean when you say "I'm not buying your quick dismissal": I never dismissed anything nor made out either that there is or isn't a large difference between the engines. I just corrected a statement that is definitely factually incorrect (and unfortunately believed by all too many).
On the actual differences between them, Chrome may be "almost identical" to Chromium, but unless you're working for Google, or have very comprehensively disassembled it, the differences is not easy to measure. What could be tiny in binary size could still be a massive change in behaviour, particularly in terms of things like telemetry.
Beyond that, they are of course not equivalent, they're just analogous. Finding a few tiny chinks in the comparison is not the same as invalidating it though. The primary analog is the approach to interop, and the resultant behaviour of the development community. Participation in standards bodies is an improvement over the IE6 days, but if you take a deeper look at Blink development, you quickly realise it's a pretty insignificant one in practice. Google controls the HTML5 spec. (the editor is a Google employee and the WHATWG is not a democratic body like the W3C), and outside of that the Blink team basically just implement what they want and specify later, rather than the reverse. The response of the development community: supporting the monopoly by ignoring interop - is pretty self-evident from links like this one.
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#26I never realized they introduced a yellow rectangle as a Pokémon.
Galaxy S7
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#27Edit: Major correction: it appears Firefox only supports clip-path behind a flag. Enabling this flag makes the experiment appear in Firefox. --- It's Webkit/Blink-only - no support for other browsers. It says it uses clip-path and variables, both supported in Firefox, so I see no compelling reason for this. Also viewing it in Chrome, I don't see anything that would actually require the use of clip-path or variables -…
Why is this currently #6 on the HN front page? Because someone took time to make this, and we tend to approach Show HN projects with an open mind. If it doesn't work on your browser, then try another one. The OP isn't asking you to buy anything or force anything down your throat.
I understand, as others have said elsewhere, that it's just an experiment, and as such cross-browser support isn't as much of a priority - it's not a product that people need to work. I've made plenty of experiments myself that only work in one browser.
However, for many experiments like this, they're doing something somewhat novel using a tech a single browser has just introduced - in those cases, it's limitations that lead to lack of interop. In this case, it just seemed a bit disappointing. That is subjective of course, but it was my - I think warranted - first reaction.
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#28Edit: Major correction: it appears Firefox only supports clip-path behind a flag. Enabling this flag makes the experiment appear in Firefox. --- It's Webkit/Blink-only - no support for other browsers. It says it uses clip-path and variables, both supported in Firefox, so I see no compelling reason for this. Also viewing it in Chrome, I don't see anything that would actually require the use of clip-path or variables -…
Unfortunately Firefox only supports clip-path behind a flag.
I was unaware of this. Thanks for the info. Edited.
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#29Earlier quoted context omitted.
Why is this currently #6 on the HN front page? Because someone took time to make this, and we tend to approach Show HN projects with an open mind. If it doesn't work on your browser, then try another one. The OP isn't asking you to buy anything or force anything down your throat.
I understand, as others have said elsewhere, that it's just an experiment, and as such cross-browser support isn't as much of a priority - it's not a product that people need to work. I've made plenty of experiments myself that only work in one browser. However, for many experiments like this, they're doing something somewhat novel using a tech a single browser has just introduced - in those cases, it's limitations t…
OP provided the source. Why not make a pull request and make those implementations and submit then back? Would be a good learning opportunity for some, no?
Re: Show HN: CSS Pokemon – created with clip-path and CSS variables
#30Damn cool, I just love polygon cuts! CSS has become quite powerful in the last few years. Guess we're not so far from being able to replace images/icons/logos with "design code" written in CSS in the coming ten years.
Here's a book on ABCs for babies done entirely in CSS: