Bob wrote:
> On Wednesday, May 22, 2013 3:55:14 PM UTC-5, Thomas 'PointedEars' Lahn
> wrote:
It's attribution _line_, not attribution novel.
>> Bob wrote:
>> ^^^^^^^^^^^^^^^^^^^^^^^^
>> Please fix that.
>
> I think I have. Please let me know if I did not fix it.
It is better now, but your full name would be even more polite (and less
ambiguous, Bob #74656).
>> > I am using IE9 fully patched on a fully patched Windows 7 x64 computer.
>>
>> You should post the unforged User-Agent header field value (or
>> navigator.userAgent value) next time.
>
> How do I do this?
For example, by entering
navigator.userAgent
in the script console. STFW.
>> > IE10 won't be deployed until next year so I have to use IE9. Am I
>> > doing something wrong?
>>
>> Probably, see <news:2354532.M...@PointedEars.de>
>
> I used
groups.google.com to search for that posting but nothing comes up
> except your response to my posting.
I can see now that Google broke this useful feature in the new version, too.
You should complain about it to them.
For the time being, you have to switch back (temporarily) to the old Google
Groups with the “My settings” dropdown. (You might need to set the new
Google Groups as default first even if you are already using it for the
respective command to be displayed – they messed this up, too.) Then the
URI will be made a link to the article. That link is working here.
>> > body {
>> > width: 800px;
>> ^^^^^
>> You can't be serious. Ever heard of wide-screen displays and Responsive
>> Web Design (RWD)?
>
> I use wide-screen displays everyday. I have 2 on my desk. The width is
> fixed because of pictures. […]
Try to find another way.
>> > background: -webkit-linear-gradient(top, #C13B5A 0%, #ffffff 100%);
>> > background: -webkit-gradient(linear, left top, right bottom,
>> > color-stop(0%,#C13B5A), color-stop(100%,#ffffff));
>>
>> AFAIK the order of those two declarations should be swapped.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> -webkit-gradient(…) is the older, AFAIK less efficient, more buggy, less
>> standards-compliant function for earlier Safari versions, now deprecated:
>>
>> <
https://www.webkit.org/blog/1424/css3-gradients/>
>
> -webkit-gradient is used by old versions of chrome and safari 4 until 5.1.
Yes, I know.
> It looks like the latest version of safari is 6.04 so I will remove that
> line. I only care about browsers from the last 3 or 4 years.
Thereby unnecessarily reducing your user base; if the site is commercial,
also your customer base and potential turnover.
> IE6-IE8 will disappear next when XP dies. Vista supports IE9 but not IE10
> so that becomes least browser I care about for windows.
What kind of argument is this? Have you read and understood what I said?
Because you have messed with the list's stylesheet, see below.
>> And please do not misuse the CRE for spacing. If you need more
>> spacing, use margins and/or paddings:
>>
>> <
http://www.w3.org/TR/CSS2/box.html#box-dimensions>
>
> After addressing most of the issues you pointed out IE still does not
> display the blue background while firefox does.
The solution to that is probably in the posting I have referred to earlier.
> […]
> Here is the latest version of the code:
> […]
> html {
> height: 100%;
> position: relative;
> }
Will you *please* stop dabbling around, and RTFM for a change? Declaring a
height of 100% when the element is not absolute positioned means nothing as
the element will always be as high as the combined height of its descendants
in the same flow. Percentage values for box dimensions are always in
relation to a containing block.
<
http://www.w3.org/TR/CSS21/visudet.html#propdef-height>
One wonders how you got the idea to format the root element in the first
place.
> background-color:#336;
> color:#000;
I do not think black text on dark blue background will be overly well
readable. Do you?
> a, a:link, a:visited {
One of those three simple selectors does not belong there.
> text-decoration: none;
Generally a bad idea. Should be at most used for navigations, and then
*only* those.
> color: #fff;
You forgot to declare “background-color”.
> }
>
> a:hover, a:focus { color: yellow; }
Conceptionally OK, but consider that yellow is a signal color indicating
attention/danger, and therefore is probably not the best color to choose
here.
Also, changes in context should not be indicated by color alone:
<
http://www.w3.org/TR/WCAG/#visual-audio-contrast>
> ul {
> list-style-type: disc;
This is the initial value of that property; it does not need to be declared.
> display: list-item;
This is wrong. A list element like “ul” has ”display: list” by default, of
course. Declaring
display: list-item;
for it instead makes a list *item* out of this list, which does not make any
sense.
You do not have to declare anything at all there. Is this your CSS editor
screwing up? If yes, try Eclipse's; if no, RTFM before you code.
> […]
> <header>
> <ul>
> <li><a href="/">Home</a></li>
> <li><a href="/News.asp">News</a></li>
> <li><a href="/ContactUs.asp">Contact Us</a></li>
> </ul>
> </header>
Better, but that content *is* the navigation and so …
> <nav>
> </nav>
… this makes absolutely no sense. Read, think, code; in that order.
PointedEars
--
Danny Goodman's books are out of date and teach practices that are
positively harmful for cross-browser scripting.
-- Richard Cornford, cljs, <cife6q$253$1$
8300...@news.demon.co.uk> (2004)