19  2434 
Lachlan Hunt wrote: Brian wrote:
Gawd, those people are clueless. Take a look at this .js, found via
a link from the rollovers article:
http://www.alistapart.com/d/domtricks2/domutils.txt
So, A List Apart is actually proposing that we sniff for ua strings
to determine how to manipulate the DOM? Gawd.
If you take a look at the date, 2000-07-21, that article was written
nearly 5 years ago back when that kind of stuff was typically
accepted.
Only by the clueless. UA spoofing goes back more than 5 years.
More recent articles on ALA have generally been much more focussed on
standards compliance and best practices. So please don't discredit
the whole of ALA based on a few bad articles in the past.
The site is awash in bad practice. Just look at their css (widths in
pixels, font set to x-small, etc.). So bad that Steve Pugh put up a page
called "Taming a List Apart", with a slew of user css to fix their
broken visual design. The .js nonsense is just another symptom.
--
Brian
in comp.infosystem s. www.authoring.html, Lachlan Hunt wrote: Brian wrote: Gawd, those people are clueless. Take a look at this .js, found via a
link from the rollovers article:
http://www.alistapart.com/d/domtricks2/domutils.txt
So, A List Apart is actually proposing that we sniff for ua strings to
determine how to manipulate the DOM? Gawd.
If you take a look at the date, 2000-07-21, that article was written
nearly 5 years ago back when that kind of stuff was typically accepted.
Why is it not removed?
More recent articles on ALA have generally been much more focussed on
standards compliance and best practices.
Yes, and often fine examples on how to not do things.
So please don't discredit the
whole of ALA based on a few bad articles in the past.
Well, show us good article, telling something that is not hard to make
better.
--
Lauri Raittila <http://www.iki.fi/lr> <http://www.iki.fi/zwak/fonts>
Utrecht, NL.
Lauri Raittila wrote: in comp.infosystem s.www.authoring.html, Lachlan Hunt wrote:If you take a look at the date, 2000-07-21, that article was written
nearly 5 years ago back when that kind of stuff was typically accepted.
Why is it not removed?
Because Cool URIs Don't Change! If articles were to be deleted just
because they are considered to contain somewhat bad advice, then the
historical record would be completely lost, and people following a link
to the article from another page (or from discussions like this!) would
just be presented with a 404 response, as happens so often. Although,
even if it were properly configured with a 410 instead, which is better
than the usual 404, that's still not completely useful. Before deleting
anything from the web, there should be a really good reason for doing so. More recent articles on ALA have generally been much more focussed on
standards compliance and best practices.
Yes, and often fine examples on how to not do things.
I won't disagree with you there. So please don't discredit the
whole of ALA based on a few bad articles in the past.
Well, show us good article, telling something that is not hard to make
better.
http://alistapart.com/articles/pocket/ http://alistapart.com/articles/eatcake/ http://alistapart.com/articles/flashsatay/
--
Lachlan Hunt http://lachy.id.au/ http://GetFirefox.com/ Rediscover the Web http://SpreadFirefox.com/ Igniting the Web
AListApart is an influential site in the web development world that has been
created by a small number of very talented and very busy people. Read
Jeffrey Zeldman's "Designing with Web Standards" to see what kind of talent
exists behind this site.
The articles at ALA are dated and we are all intelligent enough to know that
the web is changing at lightening speed. Those dates are important.
It's a buyer beware situation. Something worked 3 years ago ... doesn't mean
it works now. We don't need to get all upset because there are out-of-date
ideas on the site.
Mo' Better Rollovers is such a nifty idea that even though ithe article is
dated, it is valuable .... it can be modified and brought up-to-date. I'm
grateful to Lachlan Hunt and Gus Richter for doing that for me. That menu
will be part of a major website that my firm is developing this year.
Again, thanks to both of you ....
"Lachlan Hunt" <sp***********@ gmail.com> wrote in message
news:42******** **************@ per-qv1-newsreader-01.iinet.net.au ... Lauri Raittila wrote: in comp.infosystem s.www.authoring.html, Lachlan Hunt wrote:If you take a look at the date, 2000-07-21, that article was written
nearly 5 years ago back when that kind of stuff was typically accepted.
Why is it not removed?
Because Cool URIs Don't Change! If articles were to be deleted just
because they are considered to contain somewhat bad advice, then the
historical record would be completely lost, and people following a link
to the article from another page (or from discussions like this!) would
just be presented with a 404 response, as happens so often. Although,
even if it were properly configured with a 410 instead, which is better
than the usual 404, that's still not completely useful. Before deleting
anything from the web, there should be a really good reason for doing so.
More recent articles on ALA have generally been much more focussed on
standards compliance and best practices.
Yes, and often fine examples on how to not do things.
I won't disagree with you there.
So please don't discredit the
whole of ALA based on a few bad articles in the past.
Well, show us good article, telling something that is not hard to make
better.
http://alistapart.com/articles/pocket/
http://alistapart.com/articles/eatcake/
http://alistapart.com/articles/flashsatay/
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://SpreadFirefox.com/ Igniting the Web
On Sun, 13 Feb 2005, gallery wrote: AListApart is an influential site in the web development world that
has been created by a small number of very talented and very busy
people. Read Jeffrey Zeldman's "Designing with Web Standards" to see
what kind of talent exists behind this site.
The articles at ALA are dated and we are all intelligent enough to
know that the web is changing at lightening speed. Those dates are
important.
It's a buyer beware situation.
I don't disagree with any of that...
Something worked 3 years ago ...
doesn't mean it works now.
Then they're doing it wrong. Something that worked /properly/ 3 years
ago still works reasonably well today: there are almost certainly
better ways of doing it today, and I wouldn't advise anyone to
implement 3-year-old workarounds in their new designs today, but
there should normally no cause to go re-implementing old web content
just because some browser bugs have been fixed, or some better
techniques have become feasible. Unless you really want to.
In fact I'd rather leave my old HTML2.0 content (which can be browsed
at least as well today as it could be back then) unmodified.
We don't need to get all upset because there are out-of-date
ideas on the site.
No, /my/ concern about them is that they presented techniques that
would better be rated as experimental or bleeding-edge, as if they
were fit to be used in production web pages. Some of the techniques
could even be categorised as dependent on browser bugs (and thus
risking falling flat when those bugs get fixed).
Thus tempting web page authors who hadn't applied the appropriate
degree of scepticism, into using techniques which would need long-term
maintenance, rather than ones that were resilient against future
developments. "Buyer beware", indeed.
best regards
[TOFU painlessly destroyed... You might want to consider adopting
the long-established usenet followup style. Makes discussion go much
more smoothly.]
"Alan J. Flavell" <fl*****@ph.gla .ac.uk> wrote in message
news:Pi******** *************** *******@ppepc56 .ph.gla.ac.uk.. . On Sun, 13 Feb 2005, gallery wrote:
AListApart is an influential site in the web development world that
has been created by a small number of very talented and very busy
people. Read Jeffrey Zeldman's "Designing with Web Standards" to see
what kind of talent exists behind this site.
The articles at ALA are dated and we are all intelligent enough to
know that the web is changing at lightening speed. Those dates are
important.
It's a buyer beware situation.
I don't disagree with any of that...
Something worked 3 years ago ...
doesn't mean it works now.
Then they're doing it wrong. Something that worked /properly/ 3 years
ago still works reasonably well today: there are almost certainly
better ways of doing it today, and I wouldn't advise anyone to
implement 3-year-old workarounds in their new designs today, but
there should normally no cause to go re-implementing old web content
just because some browser bugs have been fixed, or some better
techniques have become feasible. Unless you really want to.
In fact I'd rather leave my old HTML2.0 content (which can be browsed
at least as well today as it could be back then) unmodified.
We don't need to get all upset because there are out-of-date
ideas on the site.
No, /my/ concern about them is that they presented techniques that
would better be rated as experimental or bleeding-edge, as if they
were fit to be used in production web pages. Some of the techniques
could even be categorised as dependent on browser bugs (and thus
risking falling flat when those bugs get fixed).
Thus tempting web page authors who hadn't applied the appropriate
degree of scepticism, into using techniques which would need long-term
maintenance, rather than ones that were resilient against future
developments. "Buyer beware", indeed.
best regards
[TOFU painlessly destroyed... You might want to consider adopting
the long-established usenet followup style. Makes discussion go much
more smoothly.]
It's hardly worth the effort replying to you.
The articles at ALA are hugely valuable. What a drag it would have been if
they had taken that article down. It couldn't have been used to create a new
technique. When I take an article they've provided me and customize it for
my use (standards-compliant and CSS-validating) I feel like I am standing on
the shoulders of giants.
Here are a few of them: http://www.alistapart.com/credits/
Now I'm off to create a website ... don't have time to argue. Life's too
damn short!
Lachlan Hunt wrote: Lauri Raittila wrote:
in comp.infosystem s.www.authoring.html, Lachlan Hunt wrote:
If you take a look at the date, 2000-07-21, that article was
written nearly 5 years ago back when that kind of stuff was
typically accepted.
Why is it not removed?
Because Cool URIs Don't Change! If articles were to be deleted just
because they are considered to contain somewhat bad advice,
"Somewhat bad advice?" UA string sniffing is about as dumb an idea as
there is in the .js world. Nearly 5 years have passed, and it has
apparently occurred to noone at ALA just how dumb an idea it is.
There's no need to delete the document entirely. Just remove the bogus
code and replace it with something more sensible, i.e., feature detection.
then the historical record would be completely lost, and people
following a link to the article from another page (or from
discussions like this!) would just be presented with a 404 response,
as happens so often.
Only if they maintain their web collection as badly as they write advice.
Although, even if it were properly configured with a 410 instead,
Yes, at a minimum, a request for a removed document should elicit 410
Gone from the server. A better solution is to correct the obvious mistake.
--
Brian
Brian <us*****@juliet remblay.com.inv alid> wrote: There's no need to delete the document entirely. Just remove the bogus
code and replace it with something more sensible, i.e., feature
detection.
There's also the possibility of inserting an emphatic warning at the start
of the document, saying that the document's content is now considered
outdated, obsolete, questionable, or whatever you wish to say.
This might be especially relevant if the update of the content will take a
considerable time or is uncertain (as most things on Earth are).
--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html
[pointlessly excessive quoting snipped; gallery still hasn't grasped the
quoting concept]
gallery wrote: "Alan J. Flavell" <fl*****@ph.gla .ac.uk> wrote...
On Sun, 13 Feb 2005, gallery wrote:
We don't need to get all upset because there are out-of-date
ideas on the site.
No, /my/ concern about them is that they presented techniques that
would better be rated as experimental or bleeding-edge, as if they
were fit to be used in production web pages.
It's hardly worth the effort replying to you.
Yet somehow you mustered that effort. Good for you.
When I take an article they've provided me and customize it for my
use (standards-compliant and CSS-validating)
All the standards-complying and css-validating won't do a thing if the
site is broken because of bad engineering.
Now I'm off to create a website ... don't have time to argue. Life's
too damn short!
Don't let the door hit you in the ass on the way out.
--
Brian This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: gallery |
last post by:
I also cross-posted this in comp.infosystems.www.authoring.html. I think
it's more appropriate here.
I read somewhere that you can get Tim Murtaugh's Mo' Betta Rollovers to work
in Firefox using just CSS (no javascript) .
Can someone tell me how to do it?
http://www.alistapart.com/articles/rollovers/
|
by: Frances Del Rio |
last post by:
Hi, I while back I was having a problem with rollovers, even though I do
them in a very conventional way:
function roll(i) {
document.src = eval(i + "_roll.src")
} // in which value passed to function is "name" attr in img tag..
but on my home page, www.francesdelrio.com, I have rollovers like this:
function doRoll(Img,newImage) {
|
by: Leythos |
last post by:
I've got several sites that I used DreamWeaver MX to add RollOver buttons
to the pages, it also adds some javascript that pre-loads the images and
does the mouse_over and such.
In FireFox 1.0.1 when I load the page and it pre-loads the images the
status bar shows DONE. When I mouse over any item, it changes the image
properly, but the status (lower left of browser) shows "Read
www.somesite.com", it may also show "Waiting for...
|
by: Leythos |
last post by:
I have a site at http://www.bhlnet.net/opep, it's template site for
testing, it uses roll-over images that are setup/controlled by javascript.
I've just noticed that the pages seem to be stuck with READ/Waiting in the
status message. When I use IE I don't see the READ/Waiting.
If I remove the js I don't see it, if I refresh the page and don't hold
the mouse over any button I don't see it, I've tested with virgin code....
Any ideas?
|
by: old_school_skater |
last post by:
I'm new to coding and have been given an assignment from a friend to
try and get me up to speed with tables, doctypes and xhtml. The problem
I am having is that my table works fine in Firefox browsers but break
in IE6. Any tips would be greatly appreciated.
Please see http://www.skatopia.co.nz/Phil_homework_2/phil_answer2.html
ps - I wrote the code in Notepad and have been reading HTML 3rd EDITION
THE COMPLETE REFERENCE to learn from...
| | |
by: littleark |
last post by:
Hi everybody,
I have a typical javascript images preloader, it works fine both on
Firefox and on IE in my intranet (local server).
It works fine on the Internet (remote server) in IE.
In Firefox it stops before loading every image.
Does image.onload function have some problems with little images?
|
by: roN |
last post by:
Hi,
I'm creating a Website with divs and i do have some troubles, to make it
looking the same way in Firefox and IE (tested with IE7). I checked it with
the e3c validator and it says: "
This Page Is Valid XHTML 1.0 Transitional!" but it still wouldn't look the
same.
It is on http://www.dvdnowkiosks.com/new/theproduct.php scroll down and
recognize the black bottom bar when you go ewith firefox(2.0) which isn't
there with IE7. Why does...
|
by: luggi |
last post by:
See code here:
http://lsquareddesigns.com/som/collectivemedia/landing/test1.html
At the bottom, as soon as i add rollovers, the margins are getting messed up but only in firefox. can someone help??
thanks,
laura
|
by: pammyspammy |
last post by:
Hi -
Some background info:
I'm helping to redesign an internal website at work, and I've decided to use CSS, though I don't really have any experience with it. I figure now's a good time to learn...and what I know right now, I've pretty much learned in the last week or two.
At work, we have access to only two browsers, IE 6.0 and Firefox 2.0, so these are the only two browsers I can test the site in, and they're the only ones that...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
| | |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
| | |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
