February 16, 2014

site - initial tune up

TEST TEST ...

checking text formatting options ::

Heading


Subheading


Minor heading


Normal :: default bold italic underscore strike through default

SO FAR SO GOOD ...


Default Font Smallest Small Normal Large Largest
Arial Smallest Small Normal Large Largest
Courier Smallest Small Normal Large Largest
Georgia Smallest Small Normal Large Largest
Helvetica Smallest Small Normal Large Largest
Times(Default Font) Smallest Small Normal Large Largest
Trebuchet Smallest Small Normal Large Largest
Verdana Smallest Small Normal Large Largest

Default Font (to keep off the possible/unwanted formatting's automatic forward population)

BASIC HTML TAGS TEST ::
  1. <hr>

  2. <p>
    it seems the <p>-tag in ordered list is not supported - the major achievement of soon 40y IT developement Xi yaik
  3. <table>(with basic attributes)
    Row spanning TESTColumn spanning TEST
    Top-LeftTop-CenterTop-Right
    Center-LeftCenter-CenterCenter-Right
    Bottom-LeftBottom-CenterBottom-Right
    the bordercolordark & bordercolorlight attributes not showing as they shouldn't in Mz-FF (won't commit a multi-browser check up at this time)
    attributes that seem to be working :: bgcolor , border* , cellpadding , cellspacing , rowspan , colspan
    border* -- should be inherited by cells - in FF such won't happen ?
  4. <a> embedded <img>
    <img> - TEST -- everything's OK - it ponts to erroneous image source (should display as it does) -- must be re-verified after publishing ...
    it looks that the <a><img></a> has to be scripted to display right at 1-ce coz bloggers HTML-cleanup cleans up all what you intended it to be ((i love idiots - i love the republic ...))
  5. <dir>






    test ofin commonnot supportedby 'smart'-editorsa <dir> - tag ??? -- seems working ... (for now)
  6. <sup>&<sub>
    +1(1)+1(2)-1(1)-1(2) +1(1)-1(2)-1(1)+1(2)
    ? -- looks OK
  7. <marquee>
    using the <marquee> - tag slows down the performance of your website -- although i guess there was not such issue before IE7/2009CE
    -- must be re-verified after publishing ...

No comments: