18896 2012-09-17 18:49:07 +0000 Standardization status not styled to match mocks 2013-02-24 22:36:04 +0000 1 1 1 Unclassified webplatform.org skin unspecified PC All RESOLVED MOVED P2 normal --- 1 komoroske schepers eliotgra jonathan schepers public-webplatform-bugs oldest_to_newest 74002 0 komoroske 2012-09-17 18:49:07 +0000 74571 1 ssweeney 2012-09-26 20:45:39 +0000 Alex - can you attach details of what the desired state is? Maybe also a quick screen of the issue? 74588 2 schepers 2012-09-26 21:44:09 +0000 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.) 74601 3 komoroske 2012-09-26 22:56:53 +0000 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. 74607 4 schepers 2012-09-26 23:10:53 +0000 (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). 83635 5 jonathan 2013-02-24 22:36:04 +0000 New location: http://project.webplatform.org/skin/issues/1