On Wed, Jan 7, 2009 at 22:13, Keryx Web <webmas...@keryx.se> wrote: > Hannes Magnusson skrev: >>> >>> (a) using the target attribute to open links (also in user notes) in a >>> new >>> window, which requires the frameset DTD. This should really be avoided. >>> Most >>> users find such behavior annoying. >> >> I find it really annoying clicking on links that don't open another >> domain in new tabs. There is nothing more natural then to add target >> to links leading away from the current site. Common courtesy if you >> ask me. > > I am relying on research done by Jacob Nielsen and other gurus in the > usability and accessibility crowd. > > http://www.useit.com/alertbox/990530.html
In 1999 no browser supported tabs, and you therefore couldn't configure your browser if it should open a new window or tab. If a page is not explicitly marked as "pointing outside of this domain" how is the user supposed to know she isn't still browsing the same website? By opening a new tab/window (user preference) it is very obvious you are going away from it. >>> (d) Notes are marked up as blockquotes. They are not quotes. >> >> Ouh? The user said these things, why is that not a quote? > > I was not referring to user submitted notes, but to the inline notes in the > boxes of the actual manual. > > E.g: http://se.php.net/manual/en/intl.examples.basic.php Fair enough. Its going to be annoying as hell to fix though. >>> (e) Headings in the notes are marked up with the b-element, when they >>> really >>> should be headings. This is "bed and breakfast" markup. <b> + <br> where >>> a >>> heading is the right element fir the job. >> >> You mean the "<small>User Contributed >> Notes</small><strong>page-name</strong>"? > > Once again I was referring to the notes in the actual manual, but it will > apply to user notes as well. Which heading in notes? The actual "Note:" text? Its not a heading. Didn't you say in previous mail that <strong> should be used for WARNING and such things like that, and <b> in othercases? I classify that "Note:" under the latter. In some cases there is a "title" accompanying the "Note:" string, that really should be using some sort of title element (which doesn't exists). Its not a _heading_, its just a "Hey, just in case you forgot". >>> Minor gripes: >>> >>> (a) Anorectic anchors: >>> >>> <a name="87685"></a> >>> <div class="note"> >>> >>> Should be shortened to: >>> >>> <div id="87685" class="note"> >> >> Browser don't support it. They don't even support <a name="..." />... >> and IDs cannot be integers, but names can :) > > Stupid me, not noting that the ids were integers! > > <div id="_87685" class="note"> > > Is however legal and will work in all browsers. Is that an option? No, it would break brazillions of links#fragments to the notes. >>> (d) Redundant classes? >>> <em class="emphasis"> When is <em> not used to denote emphasis? >> >> This is application generated markup. It *must* to be possible to >> distinguish docs/generated markup to regular markup. > > Would it not be easier to put that once and for all on the containg element? > E.g. <div class="generated"> > > I'll add one more place where markup can be reduced. On pages such as > http://se.php.net/manual/en/array.constants.php we have a redundant > span-elements in the dt and perhaps also the dl elements. Why not apply the > class directly to dt and dd? Because there won't be a term or paragraphs there in all cases. We are generating million lines of extremely semantically correct format to a format that doesn't even understand semantics. I would really prefer to add few hundred thousands of extra classes, which contain massive semantics, with the extra side effect of making it possible to style things down to a single word in a specific paragraph. -Hannes
