Skip to Content

First of all this weblog is meant more as a driver for discussion rather than an attempt to sound like it’s the answer to all your problems – which it most certainly is not.<br><br> 

The story begins in a little company called Suncor, where I work, obviously.  And, over the past month or so, we’ve been tackling the wonderful task of migrating from the Ep5 .NET Custom iView to the Ep6 URL iView concept – oh what fun!<br><br>

Anyhow, I and my colleagues came across a bunch of ASP-based content that was not rendering properly in our current EP6 SP6 environments.  For one, some of the content was getting truncated or rather, HTML tags were not being properly closed and as such we saw some HTML exposed as plain text (like the odd “>” character).  Now we nearly pulled all our hairs out trying to figure out a way, without a full re-write of the ASP code, to clean up those erroneous tags and so forth.<br><br> 

Well, yesterday I came across a little idea that I found worked the magic, at least for now.  I noticed a series of ‘span’ tags throughout one of the pages, but no ‘div’ tags surrounding it (I’m sure it is common to have ‘span’ tags surrounded by ‘div’ tags – but then again I’m no expert on this).  Well, I threw a opening ‘div’ tag at the top of the html document and a closing ‘div’ tag at the end.  That seemed to partly resolve the problem – no truncation, but still those partial tags.<br><br> 

When I viewed the source code, most of the content that appeared in the header was displayed nicely (formatted nicely, across various lines of text), but the actual portion that represented the HTML was displayed as a single long stream of text (this is the disadvantage of using the ‘Response.Write’ statement in ASP).  Correct me if I’m wrong, but I’m sure most editors and web browsers likely have a upper limit to the amount of html text that they can process in a single line, and I’m sure that is what caused some of the tags to not appear correctly.  So, I threw a bunch of the following statements throughout the body of the code that rendered the HTML:<br><br>

<% Response.Write Chr(10) & Chr(13) %><br><br>

And, that seemed to do the trick.  Now, I’m not the one who could even remotely come to a profound conclusion as to why this worked, but my gutt tells me that it is to do with line length limitations in the web browser.  So, am I on the right track, or could I have opened up another can of worms?  Maybe a re-write in something like Java or .NET would have been better (especially considering this ASP code resided on a .NET server).  Your thoughts, suggestions, mockery of my so called wisdom (just joking)?<br><br>

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Anonymous
    The line lenght limit is something I have not heard of before, although it sounds possible – browser should be able to handle long lines, but who knows … 🙂

    As for your guess that span-tags are always surrounded by div-tags – you’re the first one to mention that …
    If you would always use div around a span, then what would you need the span-tag for? There is nothing you can do in a span that you can’t do in the div-tag. The difference between these two elements is this:
    A div-tag starts in a new line of your text, whereas the span-tag lies within your continous text without adding line breaks to your visible output.

    Max

    (0) 
    1. Viswanath Naidu Post author
      Hi Maximillian,

      I found out that this is acually due to a proxy setting in our environment for allowed domains.  Since the new domains for our new Ep6 environments were not configured in our IE browsers, that is what was contributing to our text truncation – so neither code, nor a URL iView issue – solely a proxy setting – isn’t that weird?

      (0) 

Leave a Reply