Talk:Main Page
moved off front
Refresh for random design (and our original (cf. javascript of this frame) on average about a quarter of the time).
TODO Status bar is apparently deprecated. Change the php include to show the current style if mouseover the reference to it (which will become a link).
TODO: doesn't work framed apparently, looks like getting what would be shown randomly on the domain landing.
Root (talk) 15:11, 5 July 2021 (UTC)
Decided to change the Chosen One periodically
Was #198 due to color match up till now. Root (talk) 15:27, 3 May 2021 (UTC)
Designs that don't render the login link
About 10% of the designs hide the login link, which of course isn't a part of the original CSS. I think most of them have been identified by now, and give an alert. Root (talk) 20:38, 15 January 2019 (UTC)
Seeing more rendering failures
Not here but in the plain perimeter landings, and only on a first load, I think perhaps the original implied a timing that is gone. Will address if persists but it's not as bad the pre HTML5 situation noted below was and the design doesn't matter, it's just whatever hits first, it seems like maybe < 5% Root (talk) 12:18, 25 May 2018 (UTC) (post dated)
- This turned out to be a known CSS loading / rendering timing problem which was partially but not completely addressed and the solution may have been wiped in subsequent reworkings. Frequent in some corner cases but in general a few %, transient, and not worth fixing. Root (talk) 00:20, 6 February 2020 (UTC)
Crediting the current design
Originally the official number (except for my original design) was displayed in the status bar of most browsers. The status bar seems to have been largely eliminated though so I changed it to a mouseover of the words "random style" in the body of the document. My design shows a number of times determined by the javascript, currently about 10-20% of the time and for reasons unclear (i.e. the detailed behavior of the random function that causes it) they tend to bunch together. Root 06:14, 4 December 2010 (UTC)
Fault rate
There is a rate of failure on the display of CZG designs . There are different causes. One is that the user agent may simply fail to retrieve or render the design at all. In that case you see just the text with essentially no style and black and white text. The other is that a design may load but not render correctly due to my changed XHTML in which case usually some part of the design "messes up". I know of no cases where the whole design fails when it is retrieved and a rendering is attempted. Failures of both kinds together as well as the consecutive appearances of my design occur about 10% of the time. Rate may be higher on "mess ups". To see, use the feature above to see the number of the design, go to the actual CZG, and look at the design. Sometimes although a design looks OK here, there are things missing which you will see there. Root 01:31, 9 December 2010 (UTC)
- Did however match the php up to the current HTML Shea is distributing and that seems to have much improved the rendering, taking the "mess ups" of all kinds to the low rate I thought was present when starting this thread. Root 01:04, 10 December 2010 (UTC)
- i.e. 2-3% maybe as high as 5-6 depending how close you look. Root 00:09, 23 December 2011 (UTC)
- And of course they should all break standards compliance. It's of no concern to me here, and for that matter, anywhere, except someplace it is raised as an issue, i.e. by virtue of some client/external requirement. Root 20:01, 13 May 2012 (UTC)
- Pleasantly enough, the move to HTML5 and other changes have greatly reduced the exceptions. They are a fraction of a percent by now I think and mostly browser rendering or transmission errors. While there are still some places where the altered content munges the design, I'm no longer tracking them (although the mechanism mentioned in The Chosen One sources should still work). Root (talk) 00:10, 28 November 2013 (UTC)
Standards Checks
These fail, I've not really given it much attention, mostly tedious niggling shit. I don't want to address this other than thru the CL-MCP CL-XSL component here and may do so later. The standard CZG does appear the pass the ones I tried. Root 01:50, 10 December 2010 (UTC)
- Updating this to reiterate and clarify. I don't want to worry with standards compliance in original detailed codings. It should fall out of use of some underlying infrastructure in generated code and possibly in hand written where that is a specific desiderata to which resources are allocated. Root 10:16, 19 July 2012 (UTC)
CMS Account Creation
Disabled new account creation due a link spammer from some "social bookmarking service" in Texas. If you want an account send me an email and I'll create it. Root 09:42, 5 September 2011 (UTC)
See Talk:Programming Practice Root 20:28, 3 January 2012 (UTC)
Test
CZG 10 year reactivation (breaking changes)
sometime in the last week apparently changes were made at the CSS Zen Garden that break the random display of the content there. I've temporarily reset everywhere so only my original style shows.
CSS Zen Garden will show the same styles (at the actual CZG, and I will restore the function here if I can. I don't believe there's any problem with including the random styles, if anything I'm giving the CSG designers free advertising. I may just drop this because, not sure it's worth the trouble anymore, although it did work well for around a decade. Root (talk) 01:48, 13 May 2013 (UTC)
- Dave Shea says that he's making changes, so will leave at least until the dust settles. Root (talk) 02:40, 13 May 2013 (UTC)
- Have pulled the state from github, adjusted for my use, a few more glitches to clear but have taken the alert off when done because this is now unchanging in my domains. The new CZG base stuff seems to work better so there's actually less breakage now I think than before CZG reactivated. Root (talk) 23:36, 13 May 2013 (UTC)
