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 862 - Implement "Tabtastic" for Result pages.
Summary: Implement "Tabtastic" for Result pages.
Status: RESOLVED WONTFIX
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-02 21:11 UTC by Terje Bless
Modified: 2009-01-29 16:00 UTC (History)
1 user (show)

See Also:

Attachments

Description Terje Bless 2004-09-02 21:11:47 UTC 
Need to implement "Tabtastic" http://phrogz.net/JS/Tabtastic/index.html for
Results pages to try to alleviate som HI concerns with current design.

If this pans out we'll also need to get a license grant from Gavin Kistner
to make sure we can use the modified Tabtastic code under the W3C License.
Comment 1 Olivier Thereaux 2004-09-03 04:44:02 UTC 
Good idea, + alternate stylesheets and style switch.

Is it more a "check" or a "website" thing?
Comment 2 Terje Bless 2004-09-03 04:54:53 UTC 
It's a "User Interface / Templates" thing, but "check" was as good a
Component as any. :-)
Comment 3 Terje Bless 2004-10-12 19:29:19 UTC 
Won't make it for 0.7.0.
Comment 4 Olivier Thereaux 2007-02-19 11:37:44 UTC 
Now that I've used tabtastic extensively, I note that using it means that anchors to parts of the document that are not in the same "tab" would not work, e.g no way to link from an error message to the line in the source display. 

For me, that is a showstopper. Voting for WONTFIX.
Comment 5 Terje Bless 2007-02-19 15:05:40 UTC 
(In reply to comment #4)
> For me, that is a showstopper. Voting for WONTFIX.

Or an RFE/needspatch for Tabtastic.
Comment 6 Olivier Thereaux 2009-01-29 16:00:48 UTC 
tabbed not so hot any more. I think the result UI can still be improved, but this particular idea should be shelved.