4
edits
Gecko:Border collapse: Difference between revisions
m
update link
m (update link) |
|||
| Line 110: | Line 110: | ||
I think all this silliness with blending borders with diagonal lines is caused by those trying to formulate its workings not having any use for it personally. Not to be too abrupt, but if one is not actually using the collapsed border model and trying to take advantage of sensible conflict resolution in one's own work, one is just going to come up with a bunch of silly rules suggesting funny diagonal lines at intersection points. I find it absurd, especially when I see such nonsensical renderings as in 325074. It makes me wonder if anyone is '''actually using the collapsed border model at all'''. | I think all this silliness with blending borders with diagonal lines is caused by those trying to formulate its workings not having any use for it personally. Not to be too abrupt, but if one is not actually using the collapsed border model and trying to take advantage of sensible conflict resolution in one's own work, one is just going to come up with a bunch of silly rules suggesting funny diagonal lines at intersection points. I find it absurd, especially when I see such nonsensical renderings as in 325074. It makes me wonder if anyone is '''actually using the collapsed border model at all'''. | ||
I'm working on a page that's been begging for collapsed borders to come along for years. Now that they have, the corner resolution is completely irrational. Check out http://www.dayah.com/periodic/ | I'm working on a page that's been begging for collapsed borders to come along for years. Now that they have, the corner resolution is completely irrational. Check out http://www.dayah.com/periodic/ around the bottom where the blue line wraps the rare earths. Why are the black corners jutting into the spanning blue lines? What insane algorithm would see three edges meet in the shape of a T, with two of them colinear, and decide the interloping vertical line should win the corner? --[[User:Lucent|Lucent]] | ||
Sharing between borders of same weight is IMHO critical for people who use double borders (or groove, ridge, etc...). Furthermore, when there is no mean to decide which border should win, instead of "punishing" the "bad designer" with an arbitrary winner, why not just do something useful (double borders, etc...) ? If the designer is not pleased by the rendering, he will change his table for a correct design. (Nota: I based some of my comments on a wrong assumption, see the edit of border sharing note above, so I now think that we definitively shouldn't share the corner between borders of different widths, because there is no mean to defeat this) --[[User:frnchfrgg|FrnchFrgg]] | Sharing between borders of same weight is IMHO critical for people who use double borders (or groove, ridge, etc...). Furthermore, when there is no mean to decide which border should win, instead of "punishing" the "bad designer" with an arbitrary winner, why not just do something useful (double borders, etc...) ? If the designer is not pleased by the rendering, he will change his table for a correct design. (Nota: I based some of my comments on a wrong assumption, see the edit of border sharing note above, so I now think that we definitively shouldn't share the corner between borders of different widths, because there is no mean to defeat this) --[[User:frnchfrgg|FrnchFrgg]] | ||