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 18896 - Standardization status not styled to match mocks
Summary: Standardization status not styled to match mocks
Status: RESOLVED MOVED
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: skin (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Doug Schepers
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-17 18:49 UTC by Alex Komoroske
Modified: 2013-02-24 22:36 UTC (History)
3 users (show)

See Also:


Attachments

Description Alex Komoroske 2012-09-17 18:49:07 UTC

    
Comment 1 Scott Sweeney 2012-09-26 20:45:39 UTC
Alex - can you attach details of what the desired state is?  Maybe also a quick screen of the issue?
Comment 2 Doug Schepers 2012-09-26 21:44:09 UTC
The requires the addition of a "page title" to all page fields (in addition to the URL "shortname").

(We can't do the right styling otherwise, for complicated reasons.)
Comment 3 Alex Komoroske 2012-09-26 22:56:53 UTC
I'm not sure I understand comment 2 totally.

Doug, are you saying that this will only be possible once we stop showing the built-in page titles (the automatically generated H1s based on URL), and instead show a Page Title parameter there?

If so, that might require us to file another issue to suppress those built-in H1's on pages with templates in use.
Comment 4 Doug Schepers 2012-09-26 23:10:53 UTC
(In reply to comment #3)
> I'm not sure I understand comment 2 totally.
> 
> Doug, are you saying that this will only be possible once we stop showing the
> built-in page titles (the automatically generated H1s based on URL), and
> instead show a Page Title parameter there?
> 
> If so, that might require us to file another issue to suppress those built-in
> H1's on pages with templates in use.

Alex, yes, that's it exactly. The way the body content is produced, we have limited control over where the standardization status can be displayed. Once we take control of the H1 (and hide the old one), then we can correctly position the standardization status and quickview browser support symbols (both of these need to be before the flags, btw).
Comment 5 Jonathan Garbee 2013-02-24 22:36:04 UTC
New location: http://project.webplatform.org/skin/issues/1