also sprach Thibaut VARENE <[EMAIL PROTECTED]> [2008.03.09.1604 +0100]: > > Could you please tell me why you insist on hardcoding the default to > > an absolute value? What are you trying to achieve? > > I missed that part in my previous answer. > > I'm not trying to achieve anything. I'm providing a default CSS > which renders correctly and which I'm ready to maintain.
Have you inspected the patch I sent? How does it not render correctly or isn't maintainable? > But that [the fact that you can customize] doesn't mean that > I have to accept your changes and make them the new default. Obviously not. In this case, however, I maintain that you should avoid the use of absolute font sizes and switch to relative font sizes. Here are some other resources, which I hope do a better job at convincing you: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990324/#tech-relative-units Use relative rather than absolute units in markup language attribute values and style sheet property values. [...] For example, in CSS, use 'em' or percentage lengths rather than 'pt' or 'cm', which are absolute units. http://www.w3.org/TR/REC-CSS1#length-units : Absolute length units are only useful when the physical properties of the output medium are known. http://style.cleverchimp.com/font_size_intervals/altintervals.html Desperate or naive designers usually seek relief in inflexible pixel or print-specific absolute units such as points instead. [...] Specifically, the Web Accessibility Initiative's guidelines recommend the use of relative "em" or percentage lengths rather than absolute lengths such as "pt" or "cm". http://meyerweb.com/eric/articles/webrev/199912b.html The thing about absolute sizes is that they'll never change regardless of what the user does (short of turning off style sheets, of course). Once the absolute-size keywords are used on an element, that element's font size is locked. If users try to resize text through their browsers, elements with an absolute font size won't change, but non-absolute elements will. This prevents users from making your page's text larger if they need to see it more clearly, or smaller if they think it's too big. http://wilk4.com/webdevres/fontcss3.htm: Avoid the absolute (named, pt, px) CSS size controls since they are most buggy and remove user flexibility. http://mykiss.de/ch05_03.htm In general, these sizes are precomputed by browsers and do not change once they have been computed. Thus, if a browser considers x-large to be 27px, then it will be that size no matter what happens. This is a shame, because it would make far more sense (and be more in line with the aims of CSS) to have the absolute sizes recomputed whenever users change their browser preferences. Further complicating the situation is the fact that different user agents can assign the "default" font size to different absolute keywords. Take the Version 4 browsers as an example: Navigator makes medium the same size as unstyled text, whereas Internet Explorer assumes that small text is equivalent in size to unstyled text. Despite the fact that the default value for font-style is supposed to be medium, Internet Explorer's behavior isn't quite so wrongheaded as it might first appear. also sprach Thibaut VARENE <[EMAIL PROTECTED]> [2008.03.09.1558 +0100]: > FYI, it seems to me that as the programmer and maintainer of the > package, I get to decide whether a bug is one or not and therefore > if I should close it or not. I'd appreciate if you let me handle > my packages as I see fit. Well, I agree and I would like to apologise. Nevertheless let me say that you gave me the impression that you were unwilling to even consider the issue and thus just simply closed the bug. The bug is not about being able to change styles or about getting my preference into the defaults, it's about the use of absolute sizes when you should be using relative sizes. I consider the use of absolute sizes a bug, and I am not alone. Thus, when you closed the bug without actually talking about the issue, then I felt compelled to reopen it. I hope you understand now. And here is some other stuff about multiple CSS: > The program was designed in order to be fully customisable by the > end user (you) through the handling of various CSS. If you don't > like the one I provide (for whatever reason, taste, disability or > whatever), you *CAN* tune it to your liking, because that's > a *design feature* of the software meant precisely for that > reason. Well, I know it's supposed to support multiple CSS, but I never got it to work. I believe there was another bug report about that. By default, it only looks in /usr/share/mod_musicindex, so if I wanted to provide my own styles, I would need to write them into /usr, which is not really acceptable. Thus, I have to symlink-mirror the entire directory elsewhere to be able to add a new file properly: /etc/apache2/sites-enabled/tunes.oerlikon.madduck.net: Alias /musicindex/ /srv/music/.looks/ /srv/music/.looks/: lrwxrwxrwx 1 madduck music 39 2008-03-10 10:17 directory.png -> /usr/share/mod_musicindex/directory.png lrwxrwxrwx 1 madduck music 35 2008-03-10 10:17 fetch.png -> /usr/share/mod_musicindex/fetch.png lrwxrwxrwx 1 madduck music 37 2008-03-10 10:17 fetchok.png -> /usr/share/mod_musicindex/fetchok.png lrwxrwxrwx 1 madduck music 37 2008-03-10 10:17 general.png -> /usr/share/mod_musicindex/general.png lrwxrwxrwx 1 madduck music 40 2008-03-10 10:17 musicindex.css -> /usr/share/mod_musicindex/musicindex.css lrwxrwxrwx 1 madduck music 41 2008-03-10 10:17 right_arrow.gif -> /usr/share/mod_musicindex/right_arrow.gif lrwxrwxrwx 1 madduck music 33 2008-03-10 10:17 rss.png -> /usr/share/mod_musicindex/rss.png lrwxrwxrwx 1 madduck music 37 2008-03-10 10:17 shuffle.png -> /usr/share/mod_musicindex/shuffle.png -rwxrwxrwx 1 madduck music 35 2008-03-10 10:17 sound.png -> /usr/share/mod_musicindex/sound.png wrwxrwxrwx 1 madduck music 37 2008-03-10 10:17 soundok.png -> /usr/share/mod_musicindex/soundok.png -rw-r--r-- 1 madduck music 57 2008-03-10 10:14 tunes.css Unfortunately, contrary to the documentation, musicindex doesn't really care: piper:~> GET http://tunes.oerlikon.madduck.net/artists/ | grep css <link rel="stylesheet" title="default" type="text/css" href="/musicindex/musicindex.css" /> <a href="http://jigsaw.w3.org/css-validator/check/referer";> <img src="http://jigsaw.w3.org/css-validator/images/vcss"; Cheers, -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "i am not in favour of long engagements. they give people the opportunity of finding out each other's character before marriage, which i think is never advisable." -- oscar wilde
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
