-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-title and update H63 (Using the scope attribute to associate header cells and data cells in data tables) #2515
Conversation
1. remove references to XHTML. 2. remove references to HTML 4.01. 3. remove references using the `scope` attribute on `td` elements, which isn't part of the HTML Living Standard anymore. 4. remove some questionable content on using the `scope` attribute where authors didn't use a th element because they don't like the way it looks or have used CSS to make the text bold instead. 5. Code example: 1. change names so they’re not all male. 2. remove border attribute on table. 3. remove Fax column. 4. Change “#” to “number”. 6. Fix broken links and typos. 7. Update Procedure: 1. Change feels overly "wide" as it specifies "for each data table” rather than tables that need to use the `scope` attribute. 8. Update Resources links to point to Living Standard. 9. Marked up code as `code`. 10. Re-title document from “Using the scope attribute to associate header cells and data cells in data tables” to “Using the scope attribute to associate header cells with data cells in data tables”.
Her is a githack-rendered view of revised H63 |
Do you mean the row headers not being the first cell of each row? If so, they already aren't. For example: <tr>
<td>1.</td>
<th scope="row">Charlotte Smith</th>
<td>412-212-5421</td>
<td>Pittsburgh</td>
</tr> If you don't mean that, can you maybe provide a code example? The table on that updated page is the same as the existing one, but with changes to people's names and I removed the "fax" column. That doesn't mean we can't update it further. |
@fstrr sorry, forget it, I didn‘t look closely enough. The example is fine! |
Discussed on backlog call 10/27/2023. |
that's a sign that the conflict is too complex to be resolved just by editing here on the web. you'd need to resolve it on a computer (switching to the branch, editing the files in conflict, committing, then pushing again to the branch) |
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Closes #2514