James Byrne wrote:
As a side issue, in getting the input box ids to work with label ids as
I specified in the templates, I discovered that I had misread the
FormHelper api. I uncovered my mistake by writing a few tests to
exercise this feature as Rails own test/form_helper_test.rb did not.
Andrew Premdas wrote:
> The key phrase is semantic meaning. Its good to use CSS to give semantic
> meaning to things that appear on web pages. Not only can these id's or
> classes be useful for using with screen readers, they should be stable
> things that don't change even if the design of the pag
The key phrase is semantic meaning. Its good to use CSS to give semantic
meaning to things that appear on web pages. Not only can these id's or
classes be useful for using with screen readers, they should be stable
things that don't change even if the design of the page does. It should be
easy to s
On Mon, Mar 9, 2009 at 12:08 PM, James Byrne wrote:
> Zach Dennis wrote:
>
>> In my experience relying on the syntactic details of the page is
>> extremely brittle and cumbersome. ... Some tags have both syntactic
>> and semantic meaning, such as forms, labels, fieldsets, and anchor tags.
>>
>
> I
James Byrne wrote:
Zach Dennis wrote:
In my experience relying on the syntactic details of the page is
extremely brittle and cumbersome. ... Some tags have both syntactic
and semantic meaning, such as forms, labels, fieldsets, and anchor tags.
Is it "brittle" to test for specific css selecto
Zach Dennis wrote:
> In my experience relying on the syntactic details of the page is
> extremely brittle and cumbersome. ... Some tags have both syntactic
> and semantic meaning, such as forms, labels, fieldsets, and anchor tags.
>
Is it "brittle" to test for specific css selectors that are tie
