SunUp wrote:
When I could not find what I was looking for I was told: "I recommend that this issue in this case has not been a usability issue but instead has been a logic issue on the clients side, and I would recommend that you re-attend year 10-12 english classes in order to know this in future cases."

They obviously fail to understand the concept of usability. It's not about their ability to use the site, it's about the user's ability, and the fact that they have chosen to completely disregard this usability issue is astounding.

When I complained about horizontal scrolling I was told: "I would recommend that you take a look around the real world, not just your own room and classroom, and see that these days even seniors are using the resolution of 1024x768.

They need to realise that screen resolution is irrelevant. I suggest you inform them that it's the viewport size that matters, and even if a user has their screen resolution set to 1024x768 or higher, their browser window may not be much larger than 800px wide, either because they don't maximise it or they use a side bar or anything else that reduces the viewport size.

Personally, on my 1280x768 screen, my browser sits at around 900px wide. When I used to use a 1024x768 screen on older machines, it would have been less than 800px, because I don't like maximised windows.

And you do have a choice, you have the choice of increasing your resolution, or alternatively to scrolls when you want to see anything to the left or down on the website.

How is that a choice? In their case, that would be more of a requirement to effectively use their site! Perhaps you should politely remind them of the meaning of the word "choice".

When I commented on the huge amount of javascript in the <head> I was told: "unobtrussive javascript does not work on a number of browsers short of the newest,...

That's a load of rubbish. There are, of course, some features that won't work in older browsers, but that doesn't mean unobtrusive script cannot be written for them.

Javascript pulled from linked files doesn't work in some browsers?

I don't think either of you fully grasp the concept of unobtrusive javascript. It is not merely script which has been externally linked, it is one that exhibits no obtrusive behaviours and degrades gracefully when not fully supported or not supported at all. It is, in fact, entirely possible to have unobtrusive javascript that is contained wholly within the document, rather than an external file, although an external file is considered to be best practice.

As for the CSS that was in the <head> (body {margin-left:0px;margin-top:0px;margin-right:0px;margin-bottom:0px): ... ".. could not be solved with a simple margin:0 as you have stated, which is only the newest standard in relation to this issue,

I would like to know where they got this information from. The 'margin' shorthand property has been around for as long as the individual properties have been. They all exist as part of CSS 1 and have been reasonably well implemented in browsers. Although there are many box model related bugs, AFAIK none of them relate to the use of 'margin' instead of 'margin-top', ' -right', ' -bottom' or ' -left'.

but which does not resolve the issue in the browsers that this code is targetted at.

Ask them to name the browsers that they believe the 'margin' shorthand property (or, indeed, any other feature they claim can't be used) will not work in.

As to validation: "the W3C are self-appointed, and the standards they impose are self-regulated and are only recommended standards.

While that is technically true and there are some cases where the W3C recommendations don't reflect the interoperable behaviour found in most browsers, their standards need to be followed as closely as possible to achieve maximum interoperability.

--
Lachlan Hunt
http://lachy.id.au/

******************************************************
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************

Reply via email to