CSS strikes again (hard)
-
Not so long ago, CSS struck me with its demonic spells (well the blame goes to mickeysoft) Though I managed to kill it and bury it. And this time.. Looks like the demon has come back to haunt my layout from the dead. Rising from the graveyard where I tried to bury it (aka CSS flexbox) My buttons are suddenly top-aligned. And I'm getting no clue why. Interstingly, I have not touched my CSS in any way since my last demon slaying. Git diff has just confirmed that. So what ghost does this! -_-
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
-
Not so long ago, CSS struck me with its demonic spells (well the blame goes to mickeysoft) Though I managed to kill it and bury it. And this time.. Looks like the demon has come back to haunt my layout from the dead. Rising from the graveyard where I tried to bury it (aka CSS flexbox) My buttons are suddenly top-aligned. And I'm getting no clue why. Interstingly, I have not touched my CSS in any way since my last demon slaying. Git diff has just confirmed that. So what ghost does this! -_-
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
-
Quote:
my layout from the dead
Your layout from the dead? Or are we missing some punctuation here?
Get me coffee and no one gets hurt!
Quote:
the demon has come back to haunt my layout from the dead
The demon is the thing which has come back from the dead; the layout is the thing being haunted by said demon. It could be worded better with a little rearrangement: the demon has come back from the dead to haunt my layout. No extra punctuation needed. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Not so long ago, CSS struck me with its demonic spells (well the blame goes to mickeysoft) Though I managed to kill it and bury it. And this time.. Looks like the demon has come back to haunt my layout from the dead. Rising from the graveyard where I tried to bury it (aka CSS flexbox) My buttons are suddenly top-aligned. And I'm getting no clue why. Interstingly, I have not touched my CSS in any way since my last demon slaying. Git diff has just confirmed that. So what ghost does this! -_-
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
Have you tried a different browser. Could be the browser and not CSS. No surprise there. Doing web program is write once, rewrite for each browser, even with HTML 5
-
Not so long ago, CSS struck me with its demonic spells (well the blame goes to mickeysoft) Though I managed to kill it and bury it. And this time.. Looks like the demon has come back to haunt my layout from the dead. Rising from the graveyard where I tried to bury it (aka CSS flexbox) My buttons are suddenly top-aligned. And I'm getting no clue why. Interstingly, I have not touched my CSS in any way since my last demon slaying. Git diff has just confirmed that. So what ghost does this! -_-
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
I believe you've fallen into the (non)mythical world of QuirksMode!! Quick Answer Make sure you use doctypes for all your documents, then your CSS that shouldn't work but does, won't. For far more than you want to know see : QuirksMode - for all your browser quirks[^] QuirksMode QuirksMode is when the various browsers render the same CSS HTML differently. But it is more than that: It's related to what a browser should do if the behavior isn't defined or if the HTML would make the page not render (you still want users to see your page even if you mess it up). Lucky?? It is also what happens when you get lucky and define something that hasn't been implemented properly in browsers (in relation to the W3C def) and the browser makes it work. Unlucky? It is when you get unlucky when they browser finally "fixes" your problem and breaks your CSS.
-
Not so long ago, CSS struck me with its demonic spells (well the blame goes to mickeysoft) Though I managed to kill it and bury it. And this time.. Looks like the demon has come back to haunt my layout from the dead. Rising from the graveyard where I tried to bury it (aka CSS flexbox) My buttons are suddenly top-aligned. And I'm getting no clue why. Interstingly, I have not touched my CSS in any way since my last demon slaying. Git diff has just confirmed that. So what ghost does this! -_-
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
Aside from browser differences and updates, I discovered a while back that the same page in the same browser worked on my box, but on a virtual machine it went to hell. All the input text types decided to huddle (one atop another) in the upper left corner. The cure I found for this was absolute positioning.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Not so long ago, CSS struck me with its demonic spells (well the blame goes to mickeysoft) Though I managed to kill it and bury it. And this time.. Looks like the demon has come back to haunt my layout from the dead. Rising from the graveyard where I tried to bury it (aka CSS flexbox) My buttons are suddenly top-aligned. And I'm getting no clue why. Interstingly, I have not touched my CSS in any way since my last demon slaying. Git diff has just confirmed that. So what ghost does this! -_-
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
I think that "Give up and Use Tables" would be a great name for a song.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I believe you've fallen into the (non)mythical world of QuirksMode!! Quick Answer Make sure you use doctypes for all your documents, then your CSS that shouldn't work but does, won't. For far more than you want to know see : QuirksMode - for all your browser quirks[^] QuirksMode QuirksMode is when the various browsers render the same CSS HTML differently. But it is more than that: It's related to what a browser should do if the behavior isn't defined or if the HTML would make the page not render (you still want users to see your page even if you mess it up). Lucky?? It is also what happens when you get lucky and define something that hasn't been implemented properly in browsers (in relation to the W3C def) and the browser makes it work. Unlucky? It is when you get unlucky when they browser finally "fixes" your problem and breaks your CSS.
There's a good reason why I pronounce it "CuSS".
I wanna be a eunuchs developer! Pass me a bread knife!
-
There's a good reason why I pronounce it "CuSS".
I wanna be a eunuchs developer! Pass me a bread knife!
-
I believe you've fallen into the (non)mythical world of QuirksMode!! Quick Answer Make sure you use doctypes for all your documents, then your CSS that shouldn't work but does, won't. For far more than you want to know see : QuirksMode - for all your browser quirks[^] QuirksMode QuirksMode is when the various browsers render the same CSS HTML differently. But it is more than that: It's related to what a browser should do if the behavior isn't defined or if the HTML would make the page not render (you still want users to see your page even if you mess it up). Lucky?? It is also what happens when you get lucky and define something that hasn't been implemented properly in browsers (in relation to the W3C def) and the browser makes it work. Unlucky? It is when you get unlucky when they browser finally "fixes" your problem and breaks your CSS.
IE Firefox and Chrome all report document is being rendered in Standards mode. Something was fine till the evening and now blows off.
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
-
Aside from browser differences and updates, I discovered a while back that the same page in the same browser worked on my box, but on a virtual machine it went to hell. All the input text types decided to huddle (one atop another) in the upper left corner. The cure I found for this was absolute positioning.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Wow. Thanks for pointing out.
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
-
I think that "Give up and Use Tables" would be a great name for a song.
I wanna be a eunuchs developer! Pass me a bread knife!
The layout is far too complex for a table.
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas. Carl von Clausewitz Source
