Wikipedia talk:HTML5

src: i.ytimg.com

Video Wikipedia talk:HTML5

toptextcells

Is the toptextcells class defined on the English Wikipedia? - Ã, Gadget850 ^talk 2:59, 4 August 2014 (UTC) )

@ Gadget850: not yet, I think. See MediaWiki talk: Common.css/Archive 14 # Class to replace the default valign. On dewiki, available since 2009. Helder 03:34, 4 August 2014 (UTC)

Maps Wikipedia talk:HTML5

Duplicate information

It's starting to look like Help: HTML in wikitext. Did not we recreate the wheel here? - [[ User: Edokter ]] {{ talk }} 09:24, December 6, 2014 (UTC)

It does not recreate, but there is some overlap, which happens on all the help pages. I see the point here to help update outdated markups to render the right HTML5, so this help page is much more specific. Currently built, we should add a note to Help: HTML in wikitext redirect here for further help. I've added a few cases I've seen several times. - Ã, Gadget850 ^talk 13:55, December 6, 2014 (UTC)

src: cdn.vox-cdn.com

& lt; br clear = all/& gt;

See User_talk: Yobot # Possible_bug for discussion for nearly ten years, {{clear}} is a div (element-block), {{-}} is br (inline element). -Be..anyone (talk) 13:02, February 2, 2015 (UTC)

src: i.ytimg.com

What is found

Edokter stated, "This is not about what is" found "; this is the correct syntax, even though it is outdated." The top of the article states, This project serves to set the adaptation of articles and other Wikipedia pages to HTML5 . This page is about what is found in the Wikipedia article and how to fix the problem.

"User agents are expected to support a 'clear' property on inline elements (to create br elements with obvious attributes) in the manner described in non-normative records for this effect in CSS2.1."

There are even rules to consider clear = all and clear = both are clear: both. -Be..anyone (talk) 23:45, February 9, 2015 (UTC)

Source? - [[ User: Edokter ]] {{ talk }} 00:01, February 10, 2015 (UTC)

Maybe it's not just Chrome I refuse to show & lt; blockquote cite = "http://www.w3.org/TR/html51/rendering.html" & gt; URL, but visible in the source editor; almost verbatim WhatWG Hixie's living standard as of January. Warning: this is off topic (rendering, not validity.) -Be..anyone (talk) 15:53, 10 February 2015 (UTC)

The cite attribute is always invisible, and HTML5.1 is not relevant here. - [[ User: Edokter ]] {{ talk }} 16:35, February 10, 2015 (UTC)

src: fm.cnbc.com

Large

People should not use hardcoded pixels for font sizes, because they will foil on browsers that have their fontsizes set different default shapes (16px on Windows). You can review the actual effects in Users: Edokter/fonttest. - [[ User: Edokter ]] {{ talk }} 12 : 27, February 23, 2015 (UTC)

Currently, the nested big suggestion is to use CSS with pixels. I did some testing with percentages using {{resize}} in Users: Gadget850/big. Is there an official guide? - Ã, Gadget850 ^talk 12:51, February 23, 2015 (UTC)

I checked the effect & lt; big & gt; and font size: larger; in all major browsers, and fortunately, they all resulted in a 120% right increase. & lt; small & gt; and font-size: smaller; is not very consistent, but generally produces 85%. The non-relative keywords form the letter-size: xx-small; to font size: xx-large; is encoded into 9, 10, 13, 16, 18, 24 and 32px, regardless of default font size setting and scale with browser font size. - [[ User: Edokter ]] {{ talk }} 13 : 13, February 23, 2015 (UTC)

I understand why this is complicated. On my test page, measured by JRuler:

• Firefox 36: & lt; big & gt; x 5 shows width 195px, 249% is 122px, 400% is 194px (my original choice).
• IE11: & lt; big & gt; x 5 indicates a width of 108px, 249% is 122px.

I see & lt; big & gt; x 5 is used in two articles to increase the size of Unicode characters. - Ã, Gadget850 ^talk 14:23, February 23, 2015 (UTC)

Yes, I never tested nested bigs... works in Chrome, but FF and Opera make them grow exponentially. I think this is more reason to 'ban' all usage & lt; big & gt; , especially nested ones. - [[ User: Edokter ]] {{ talk }} 15 : 41, February 23, 2015 (UTC)

The official guide of the W3C is that & lt; big & gt;... & lt;/big & gt; should be styled with the font-size declaration: larger; , see the HTML 5 specification, section 10.3.4 Contents of the phrase. - Red rose64 (talk) 16:54, February 23, 2015 (UTC)

Yes, but the problems encountered are nested. The only thing I can find is "Font style elements can be nested and they must be nested correctly." Rendering elements of a multilevel font style depend on the user agent. " [1] Which does not specify specifications on the size of nested bigs. - Ã, Gadget850 ^talk 18:12, February 23, 2015 (UTC)

I expect the font size to increase exponentially: & lt; big & gt; & lt; big & gt;... & lt;/big & gt; & lt;/big & gt; should provide a larger "made" size that is "bigger", and if in certain browsers, font size: larger; is equivalent to 120%, then 120% * 120% is 144% and nested five & lt; big & gt;... & lt;/big & gt; must provide 120% ^ 5 or 248,832% - Red rose64 (speak) 18:51, 23 February 2015 (UTC)

Add another test in User: Gadget850/great. Firefox expands & lt; big & gt; x5 is about 450% of the standard and IE11 is about 220%.

I agree with Edokter: nested big is Bad Thing (TM). - Ã, Gadget850 ^talk 23:36, February 23, 2015 (UTC)

Template ukuran font

src: i.ytimg.com

skor centering dan tag kode

Wikipedia: HTML5 # The tag parser does not list how to center & lt; score & gt; or & lt; code & gt; tags. Could this be added to the list? Bgwhite (talk) 20:36, February 23, 2015 (UTC)

Element & lt; code & gt;... & lt;/code & gt; is in line, so concentrating it as effectively and as easy as trying to center & lt; b & gt;... & lt;/b & gt; or & lt; i & gt;... & lt;/i & gt; element. As for & lt; score & gt;... & lt;/score & gt; , does not seem to recognize the class = center attribute, but there's no reason you can not do this:

ie, wrap it in & lt; div class = center & gt;... & lt;/div & gt; - Red rose64 (talk) 21:22, February 23, 2015 (UTC)

Or {{center}}, which is cleaner in markup. & lt; code & gt; is a standard HTML element used to add semantics and presentations to text: use {{center}} as you would with any other text. - Ã, Gadget850 ^talk 22:49, February 23, 2015 (UTC)

Thank you both. Bgwhite (talk) 00:13, 24 February 2015 (UTC)

src: cdn.vox-cdn.com

Statistics

It would be nice to have some sort of stats page that can keep a record of progress. I've done one for my own use for a number of attributes & amp; tags in the template space. Progress Templates. - WOSlinker (talk) 21:23, February 23, 2015 (UTC)

I do not see that we will update all markup at this point. The editor will keep using the markup they know until they are forced to change. T40487 has been open for two years: The button on the editing toolbar adds & lt; big & gt; .

I've seen some comments parsing an HTML break with a mobile browser, but I have not been able to track any details yet.

There are proposals for updating HTML automatically, but with the strange things I've seen that might break things up.

If you really want to use the obvious, change the site's CSS so that the element is wrapped in a big red error. But this will only urinate from a group of people.

But if you really want statistics, use the search links I added and track usage. I'm sure you can do something with the API, but I have no experience there. - Ã, Gadget850 ^talk 23:56, February 23, 2015 (UTC)

For & lt; font & gt; , & lt; strike & gt; and & lt; br clear & gt; tags in the article, you can see CheckWiki # 40, # 42 and # 2 respectively. There was a CheckWiki error to find the & lt; big & gt; , but not turned on at this time. Also, unlike the first three tags that have been cleared, there are tons of tags & lt; big & gt; is still left in the article. Bgwhite (talk) 00:11, February 24, 2015 (UTC)

@ Gadget850: Some outdated HTML is not corrupted in the mobile browser, but all confirmed reports about markup of this issue are never part of the formal HTML specification , such as the bgcolor = attribute of the table. This attribute first appears in the HTML specification in HTML 3.2 when it is only shown for elements & lt; body & gt;... & lt;/body & gt; ; in HTML 4 it is also displayed for certain table elements ( & lt; tr & gt;... & lt;/tr & gt; & lt; th & gt;... & lt;/th & gt; & lt; td & gt;... & lt;/td & gt; ) but flagged as no longer valid. I believe that the idea is that if it is officially described as obsolete, people will be discouraged from using it; but if it's not described at all, people might use it by copying bad practices from some of the webpages they like, oblivious to their non-universal recognition. Little like element & lt; blink & gt;... & lt;/blink & gt; (only recognizable by NetScape and Firefox) or style & lt; marquee & gt;... & lt;/marquee & gt; (IE). - Red rose64 (talk) 10:44, 24 February 2015 (UTC)

src: i.ytimg.com

Changes to search templates

The first search insource:/\ & lt; big/i takes 20 seconds. Even after I deleted i case-insensitivity, it returned 125 thousand articles. I think using a search link like that for a list of articles in the amount to be done at WP: AWB will be launched. Hi wait... they already have their own database download and there is a regexp search that will run their own automated remote editor to update/change the code.

Many searches do not work. But wait... before we fix it, how about if we agree to replace them each with their count? Run a search once , and record the amount? I do not think that public buttons are a good idea except for each push button, notes are made from count in other table columns, and the count has some public value. So I would not even recommend using prefix: A to give gawkers a quick feeling for coverage of every project detail.

Please say something here or on the project page about this search link. I have something like this happening in {{Val/unit/test}}, but their purpose is clear, unlike here. At least tell me why both the article search button and the wide-wiki search button is emptied.

I just say all this because MediaWiki says that regex search is so intense that only a few at a time are allowed to run at any time on the wiki - a regex search can actually kill a search cluster if the settings are not tweaked exactly - and that's a search insensitive even worse. And they say to always run this search with filters, never alone. For example, insource: "div align" insource:/\ & lt; div align/ - Cp r al Cpiral 06:32, July 22, 2015 (UTC)

OK, find the link. I have tightened it all with all types of filters so the regex runs fast. - Cp my r al Cpiral 08:21, 8 August 2015 (UTC)

src: cdn.vox-cdn.com

How to change wikilink color using span element?

The

• font element can change the wikilink color
  • & lt; font color = "red" & gt; [[Cosmos]] & lt;/font & gt; -> Cosmos
The span element
• can NOT change the wikilink color
  • & lt; span style = "color: red;" & gt; [[Cosmos]] & lt;/span & gt; -> Cosmos
The
• method to change the wikilink color using the span element
  • [[Cosmos | & lt; span style = "color: red;" & gt; Cosmos & lt;/span & gt;]] -> Cosmos

Is this ok? Or is there another way? --Momijiro (talk) 00:56, 4 February 2017 (UTC)

It is true that they work differently; and as far as I know, ranges must be in the link to override colors. However it can violate one or both MOS: COLOR and MOS: CONTRAST. - Red rose64? (talk) 11:03, 4 February 2017 (UTC)

Thank you OK, I understand. --Momijiro (talk) 17:01, 4 February 2017 (UTC)

Source of the article : Wikipedia