3 ms·
So basically 15 years late, CSS finally solves this problem. And coming to CSS in 15 years: adaptive design!
by cm2187 10y ago
So basically 15 years late, CSS finally solves this problem. And coming to CSS in 15 years: adaptive design!
- B1FF_PSUVM 10y agoThirty year cycle, seems about the right interval for moving bones around in the graveyard, as traditional in all kinds of fashion and research.
- edblarney 10y agoIt's generational. 30 years is enough for one generation to be replaced in whatever industry. And so we forget. Same in politics, war, fashion, tech, research, literature, art, music. Just keep those 'skinny jeans' in the back of the closet for New Years Eve 2045 ...
- phkahler 10y agoNext up: Revival of the <frame> tag!
- paulddraper 10y agocontent-src: url("http://example.org")
- ashark 10y agoI seriously wish it'd survived and been enhanced. Much AJAX in practice is used to replicate the effect of <frame>s, but slower, buggier, and with more battery drain.
- phkahler 10y agoI agree. My understanding was that it had 2 major problems. 1) you could load other sites or 3rd party content in a frame which caused confusion - browsers should not have allowed that. 2) search engines had problems with them - that's not my problem, they should have gotten smarter. May have been helped by eliminating the first problem.