Simply in the root folder, create a file:
.htaccess
then:
--start--
rewriteengine on
rewriterule ^gallery/$ gallery.php
-- end --
...or enable multiviews, which is a far slicker way IMHO...
P
Patrick H. Lauke
Web Editor / University of
Dmitry Baranovskiy
Add to this “Will search engines correctly understand such a
symbols?” The answer is “No”.
Compare:
3×4
http://www.google.com.au/search?hl=enq=3%D74btnG=Searchmeta=
3x4
http://www.google.com.au/search?hl=enq=3x4btnG=Searchmeta=
3 4
Barney Carroll
What would your mobile css change compared to the screen one?
Mostly, optimise for single column, linearised viewing. Possibly avoid very
heavy use of image replacement for larger elements.
P
Patrick H. Lauke
Web Editor / University of Salford
James Crooke
We have conducted usability testing on 100's of sites and my argument
is that when you hover over a button and nothing happens, users
sometimes think oh the button is dead
A counter argument to that:
So they'll get confused on every site that uses a button. You then change
it
Nick Fitzsimons
I once read an explanation of why CSS selectors can't do this, but I
can't find it now.
I seem to remember that the main objections were:
a) performance issues (as there is the potential, with ancestor queries, to run
very slow depending on how deep the DOM tree is)
b)
Mike at Green-Beast.com
I echo what Mel said, though I'd like to add that the label
should probably
be the same as the name (and the ID, if needed, may as well
match too).
Just being mindful that obviously, for radio buttons, the ID can't match the
name, as the former needs to be
[EMAIL PROTECTED]
I can't find the reference now, but I saw a report recently by someone
of the likes of Gartner, that reckoned it would take a year
or so before
IE7 overtook IE6.
At least part of that will be that a lot of organisations (ours included) are
working towards blocking the
Townson, Chris
Patrick H. Lauke wrote:
If the generated image also has the right alt text, you can
copy paste
if you start just before the image (just as with sIFR). The
only thing
that you can't do is select just a set of characters/words from the
replaced heading itself
Shlomi Asaf
Dean, about FieldSet its going to become Deprecated:
http://www.w3.org/TR/html4/interact/forms.html#h-17.10
aehno it wont. the *align attribute* in fieldset is deprecated,
not the fieldset itself...
P
Patrick H. Lauke
Web Editor / University
John S. Britsios
So I have visited the HTML Techniques for Web Content Accessibility
Guidelines 1.0 here
http://www.w3.org/TR/WCAG10-HTML-TECHS/#image-text-equivalent
and I was
surprised to find there an example, that is 100% identical to
one of the
images of my site.
You *cannot*
[EMAIL PROTECTED]
Surely any conforming user agent should ignore any markup that it does
not understand, so is there really any need to stop using
name, where it
is being used for 'belt and braces' compatibility?
For XHTML 1.0 (even strict), using name is still fine. Deprecated, yes, but
Jan Brasna
Right. Nowadays you should have no problems with colors
I think that, as always, this will come down to your target audience.
If you know for a fact that there are still a sizeable proportion of
your users on 800x600 with only 256 colours or similar, it's obviously
worth
Joshua Street
On 6/6/06, Patrick Lauke [EMAIL PROTECTED] wrote:
avoid that a foreground and background colour resolves to
the exact same safe colour.
And, obviously, if this is happening there's probably already enough
wrong with your design's contrast that safe colours should
Leskinen N.
Yesterday I have connected PDA to the Internet and have
looked as sites
under web-standards are well looked.
http://whale-zx.livejournal.com/8498.html
Not so well...
So...the mobile version of IE tries half-heartedly to apply some
screen CSS and fails? Quelle surprise!
Warren Cardinal
if resizing text breaks the design, why the hell allow it?
If people can't read your text, why the hell put it online?
Case in point is all these cool flash sites out there
that even I can't read, they are so tiny.
And that's a good thing?
Typography is an art
And to quote your previous message
Warren Cardinal
It's a tool
Tool indeed.
P
Patrick H. Lauke
Web Editor / University of Salford
http://www.salford.ac.uk
Web Standards Project (WaSP) Accessibility Task Force
Roberto Scano
I think that, due the deadline for comments for WCAG 2.0 Last
Call is on
31th May 2005, is best to read WCAG 2.0 and send directly
comments [1] ;-)
Time to read Joe's article: 10 minutes.
Time to read WCAG 2.0 (and its associated informative documents): 3 days?
I'm sure we
kvnmcwebn
why doesn't firefox recognize the visited state in this rule?
.navcontainer a:hover:visited
{
color:#BCB281;
}
Tried on one of my pages, and FF recognizes :hover:visited and
:visited:hover just fine.
Probably a specificity issue?
Patrick
Cole Kuryakin
As Bruce - and perhaps others - had mentioned in a few of the
replies, I
tried inherit as the background-color property on all rules
in question,
revalidated, and PERFECT. No errors or warnings at all.
As long as you're using flat colours, that's fine. Be aware, though,
Web Man Walking
I was wondering if anyone had any experience of the
best Web Standardy way of documenting Help/FAQ's etc.
There's no one way that is The Best(tm), but some ideas
would be:
- using definition lists
dl
dtQ/dt
ddA/dd
dtQ/dt
ddA/dd
...
/dl
- simply using headings/paragraphs
John S. Britsios
The guideline 31 for Accessible and Usable Web Sites, with
the title Do
not exclude labels form fields found here
http://redish.net/content/papers/interactions.html
says:
When filling out a field makes the page refresh, the software starts
reading from the top as
21 matches
Mail list logo
