Results 1 to 4 of 4

Thread: Use HTML in posts instead of vB code?

  1. #1
    Member xpatUSA's Avatar
    Join Date
    Jun 2010
    Location
    Bellville, Texas
    Posts
    423

    Default Use HTML in posts instead of vB code?

    Hello All,

    My first post here in the tech zone . .

    I'm more fluent in HTML than in vB script. But I got burned big time on another site forum when the Administrator deleted the HTML option, leaving me with 1000+ posts all with images that didn't show, lists that turned into unformatted long sentences, etc., and of course all my HTML tags rendered as plain text.

    Having said all that, I'd like to start using plain HTML in posts here on MWR - giving rise to some questions . .

    Does anyone else prefer & use "basic" HTML in posts instead of vB code?

    Are there any tags or code that should not be used apart from the obvious, like, presumably, JavaScript, frames, in-line styles(?) or similarly exotic stuff?
    cheers,

    Ted

  2. #2
    Member xpatUSA's Avatar
    Join Date
    Jun 2010
    Location
    Bellville, Texas
    Posts
    423

    Default testing use of HTML

    A Test Watch Description

    Satiné finished pure Unobtainium case with screw-in back.  Plain black dial with blue Roman numerals and date window at 3.  Silver-tone NATO-style nylon band.

    angled front view

    Thanks for looking!


    HTML Code:
    <div style="width:720px;text-align:center"><p style="font-size: 24pt;"><u>A Test Watch Description</u></p><p  style="font-size: 16pt;">Satiné finished pure <b>Unobtainium</b> case with screw-in back.  Plain black dial with <span style="color:blue;">blue Roman numerals</span> and date window at 3.   Silver-tone NATO-style nylon band.</p><p><img src="an640.jpg" alt="angled front view" style="border: thin solid #8080FF; width: 320px; height:240px;"></p><p  style="font-size: 20pt;"><i>Thanks for looking!</i></p></div>
    The backslashes in the HTML code line above were added by the forum vB processor, presumably to "escape" the in-line quote characters
    cheers,

    Ted

  3. #3
    Junior Member
    Join Date
    Dec 2011
    Posts
    1

    Smile

    enabling HTML is a serious security risk, both for the server, but also for those viewing the site. imagine a malicious javascript that reads sensitive information from your workstation and then sends it back to some source? i personally have seen a script that invisibly collects passwords and other information.

    by your own argument, vbcode is just as easy/hard as html, and so there is no extra overhead to use it. do you honestly need to include images or tables in your posts? what if you put a tag in your post? don't you think that would mess up the rendering of the rest of the page

  4. #4
    Member xpatUSA's Avatar
    Join Date
    Jun 2010
    Location
    Bellville, Texas
    Posts
    423

    Default I beg your pardon?

    Quote Originally Posted by AnkitSingh View Post
    enabling HTML is a serious security risk, both for the server, but also for those viewing the site. imagine a malicious javascript that reads sensitive information from your workstation and then sends it back to some source? i personally have seen a script that invisibly collects passwords and other information.

    by your own argument, vbcode is just as easy/hard as html, and so there is no extra overhead to use it. do you honestly need to include images or tables in your posts? what if you put a tag in your post? don't you think that would mess up the rendering of the rest of the page
    A pretty aggressive reply.

    HTML is always enabled on our host's server and we can do nothing about that. When we create a post, html can be mixed in with VB, the post still renders OK without any "enabling" action on our part.

    Does anyone NOT need to put images in their watch forum posts?

    And why on earth would anyone put javascript or even a form in a forum post, even if the forum engine would take it?

    I think you missed the point of this thread entirely.

    Namaste,
    cheers,

    Ted

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •