Seeing as though Google's new Chrome browser uses the same rendering engine
as Apple's Safari, would it be acceptable to test browser layout issues in
Chrome and assume the same CSS solutions apply in Safari? Does anyone know
of any distinct differences in CSS rendering between the 2 browsers?
Working fine first load Kristine in the UK
Winxp:
SP2
1680x1050
IE6
Kate
Forum: http://princess.invisionzone.com/index.php
Borneo: http://simplyborneo.com/borneosnaturaltreasures/
- Original Message -
From: Kristine Cummins [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent:
Not only JS, there are differences in CSS as well.
Shadows appear, but kinda buggy, not as it should. text-shadow and
box-shadow.
The rounded borders are not antialiased (as in aliased or pixelated) in
Chrome whereas FF3 and Safari handle it correctly.
And font-face doesn't work at all, whereas
I am looking for feedback on two questions, based on the simple form snippet
below.
fieldset
legendbPersonal Details/b/legend
label for=nameName:/label
input id=name type=text name=name size=30 br
label for=idID Number:/label
input id=id type=text name=id number size=10
/fieldset
Jason Grant wrote:
Ok you got both of these quite wrong for following reasons:
In the first instance you shouldn't use b or br / at all.
In the second instance you should not wrap input into label as the
label should quite clearly be used for denoting a label of an input
field and not the
I've always used label arount input fields labeltext: input type=text
//label without the for= attribute.
I've never had problems with it, and I don't think I've ever seen any
recommendation against it.
Johan Douma
[EMAIL PROTECTED]
2008/10/16 David Dorward [EMAIL PROTECTED]
Jason Grant
This is the first time for me to see someone proposing use of labelinput
//label structure.I agree that ol is not strictly necessary and that a
form is not necessarily a list, but one could argue that you are dealing
with a list of form input elements.
Read more why I do this here:
Johan – what you are describing is the correct usage in that scenario.
Thanks,
Tatham Oddie
callto:+61414275989 call:+61414275989, callto:+61280113982
call:+61280113982, skype:tathamoddie?call skype:tathamoddie, msnim:[EMAIL
PROTECTED] msn:[EMAIL PROTECTED],
Hi Guys/Gals,
I would like to get some opinion from you all, that would Flash 10 or ++
will replace JavaScript in the future?
According to this blog :
http://ajaxian.com/archives/flash-10-and-the-bad-news-for-javascript-interaction
.
I found that alot of media website started to replace
Johan Douma wrote:
I've always used label arount input fields labeltext: input
type=text //label without the for= attribute.
I've never had problems with it, and I don't think I've ever seen any
recommendation against it.
There's a discussion about some problems with that pattern at:
On Thu, Oct 16, 2008 at 9:27 AM, Charles Ling [EMAIL PROTECTED] wrote:
Hi Guys/Gals,
I would like to get some opinion from you all, that would Flash 10 or ++
will replace JavaScript in the future?
According to this blog :
Charles Ling wrote:
I would like to get some opinion from you all, that would Flash 10 or ++
will replace JavaScript in the future?
According to this blog :
http://ajaxian.com/archives/flash-10-and-the-bad-news-for-javascript-interaction.
I'm not entirely sure Christian's right that Flash 10
Read the story on that page carefully. What has happened is that flash
10 has increased restrictions over what features within the flash
plugin can be invoked via javascript. This only applies to one
specific feature (file uploads), and effects virtually no other flash
features. It does not effect
2008/10/16 David Dorward [EMAIL PROTECTED]
Jason Grant wrote:
Ok you got both of these quite wrong for following reasons:
In the first instance you shouldn't use b or br / at all.
In the second instance you should not wrap input into label as the
label should quite clearly be used for
Ok you got both of these quite wrong for following reasons:
In the first instance you shouldn't use b or br / at all.
In the second instance you should not wrap input into label as the
label should quite clearly be used for denoting a label of an input field
and not the input field itself.
Using a
Hi Ben,
I've always used label arount input fields [...]
I don't think I've ever seen any recommendation against it.
Here's one for you:
http://green-beast.com/blog/?p=254
I haven't been paying attention to this, and someone's probably already said
it (if so, sorry), but it's also worth
Johan Douma wrote:
I've always used label arount input fields labeltext: input
type=text //label without the for= attribute.
I've never had problems with it, and I don't think I've ever seen any
recommendation against it.
Support is weaker then for the for attribute, so I would avoid it.
It
I understand where you’re coming from because for some designs the legend isn’t
easy to style consistently cross-browser, and so sometimes I have used a
heading instead. However if possible, using the legend is much better.
I also used to wrap form inputs in labels for the same reason as
On Thu, 16 Oct 2008 10:49:59 +1000, [EMAIL PROTECTED] wrote:
Hi,
Seeing as though Google's new Chrome browser uses the same rendering engine
as Apple's
Safari, would it be acceptable to test browser layout issues in Chrome and
assume the
same CSS solutions apply in Safari?
Does anyone
Thank you everyone for your replies. So it seems the trusty old traditional
filedset
llegendContact Information/legend
label for=nameName/labelbr /
input id=name type=text
/fieldset
is the way to go to keep all browsers and screen readers happy. I think I can
likely lose the br / and
I don't see flash becoming a dominant technology in the future. It's
definitly not going to replace javascript.
It wouldn't actually surprise me if it is going to die off really slowly...
Only to be used in really specific cases.
Flash gets used a lot today because the flash video codec is good
21 matches
Mail list logo
