This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26639 - Having a state that is primarily stylistic (i.e. Search) doesn't adhere to separation of concerns.
Summary: Having a state that is primarily stylistic (i.e. Search) doesn't adhere to se...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-22 14:15 UTC by contributor
Modified: 2014-09-17 22:30 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2014-08-22 14:15:01 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html
Multipage: http://www.whatwg.org/C#text-(type=text)-state-and-search-state-(type=search)
Complete: http://www.whatwg.org/c#text-(type=text)-state-and-search-state-(type=search)
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/tables.html

Comment:
Having a state that is primarily stylistic (i.e. Search) doesn't adhere to
separation of concerns.

Posted from: 205.211.168.17
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
Comment 1 Ian 'Hixie' Hickson 2014-09-17 22:30:36 UTC 
It's the same as how the difference between <em> and <strong> is "primarily stylistic". It has a different semantic and thus a different style. It's entirely in line with the separation of concerns design goal.