Our front-end has a concept of screen flow, is the front-end HTML page We see, it is a whole page is the screen flow, the reason is called the flow, because it is mobile, our HTML tag, when given to the browser rendering, there will be some CSS properties, such as floating, float, For example Fix,position, they can let our HTML tags float up, is out of our screen flow, floating in two states, one is completely floating, is completely out of our screen flow, there is a semi-floating, it is not completely out of our screen flow, will be affected by other tag parameters in our HTML, such as we set a label to float, then it is floating, then there will be other side of the contents of the tag to fill the vacant part, so that we can not achieve the desired effect,
The fully floating properties are position:fixed,
The semi-floating properties are position:absolute,relative; and float,
=================================================================
Our front-end can be custom functions, that is, our front-end language does not have this function usage, but we can set it ourselves, through specific syntax requirements to do, such as
1Date.prototype.Format =function(FMT) {//Author: "%y-%m"2 varo = {3"m+": This. GetMonth () + 1,//Month4"D+": This. GetDate (),//Day5"H +": This. GetHours (),//hours6"m+": This. getminutes (),//points7"S+": This. getseconds (),//seconds8"q+": Math.floor (( This. GetMonth () + 3)/3),//Quarterly9"S": This. Getmilliseconds ()//millisecondsTen }; One if(/(y+)/.test (FMT)) FMT = Fmt.replace (regexp.$1, ( This. getFullYear () + ""). substr (4-regexp.$1. length)); A for(varKincho) - if(NewRegExp ("(" + K + ")"). Test (FMT)) FMT = Fmt.replace (regexp.$1, (regexp.$1.length = = 1)? (O[k]): (("XX" + o[k]). substr ("" +O[k] )); - returnFMT; the};Custom Function methods inside the front end
Front end, CSS