Jukka K. Korpela wrote:
Marek Mänd <ca********@mail.ee> wrote:Can the
<button><img></button>
[be] mutated via CSS
Use a submit button instead. Or, if you insist, an image submit button,
see http://www.cs.tut.fi/~jkorpela/forms/imagebutton.html
Test that the form works. _Then_ start considering styling.so, that the inner image of <BUTTON>
would entirely visually become the button itsself
Then there's hardly any point in using <button>, instead of
<input type="image">.
Well IMHO there could be some advantages:
Consider situation:
a saved pure html page without images and without stylesheets
<button type="button"><img src="unexistant"><span
style="display:none">commandbutton spare label for offsite
use</span></button>
would perform better than a <input type="image" src="unavailable">
with a tooltip. Besides tooltips everywhere in the document can be quite
frustrating. Especially amuses me all these CSS websites, that use
acronym and abbr elements quite often - one cannot even move the mouse
without annoying tooltips.... I am against flashy title tooltips, there
is a status bar for that.
Sadly <input type="image"> is by constitution about submitting form,
not as <button type="button">... Yes it can be WAd via JS, but thats
overhead.
Using hyperlinks for simulating buttons that do something on a web page
using JS - I find this approach not right because of I think of URLs as
of a way to navigate to a different page. Ofcourse when smb wants
Netscape3 compatibility then this is the way ;D
Using the <img> as an background image for buttons isnt
an option because it would crate a CSS bloat declarations.
That statement does not quite parse. But setting a background image for a
normal submit button, <input type="submit">, is of course one possibility
in styling.
Well those images for buttons would actually be different in web
application, thus for earch image a style class is too much. As icons
are much easily to be changed in serverside scripting templates than in
CSS (which just adds too much complexiti and dependancies)