Mysource Notice above doctype throws browser into quirks mode


(Byrn2lis) #1

Hello everyone,

 

Perhaps this is an easy question to answer, but it has me stumped.

 

I am designing a new simple edit interface with HTML5 and noticed that mysource notices are printed above the doctype in a design - which throws ie8 into quirks mode.

 

Example:

  1. I went to add a future status - intentionally only picking the status leaving the date and time empty
  2. Committed the page
  3. Mysource Notice prints above doctype!
<table bgcolor="#c0c0c0" cellspacing="0" border="1" cellpadding="2" bordercolor="#ff0000">
					<tr>
						<td style="background-color: #17AA92; font-size: 14px; font-weight: bold; color: #ffffff; font-family: verdana, arial, sans-serif; vertical-align: top;">
							MySource Notice						</td>
					</tr>
					<tr>
						<td style="background-color: #17AA92; font-size: 12px; color: #ffffff; font-family: verdana, arial, sans-serif; vertical-align: top;">
			To add a future status you must specify the date and time at which the status should be changed [CRON0046]						</td>
					</tr>
				</table><br/>

<!DOCTYPE html>

Is there a keyword for displaying these notices where I want or some other fix? What am I missing?

 

Cheers!

 

Lisa

 

 


(Robin Shi) #2

Simpled editing interface is quite old. We tried to implement with HTML5 parsefile but ended up with EES.


(Nic Hubbard) #3

Can you get away from using IE8? Is that a corporate requirement? It is quite old at this point.


(Byrn2lis) #4

Robin - Thanks for your reply. I was hoping this wasn't the case and rather I overlooked something. We have quite a customised 'administration area' that at this stage, rules out EES (training publishers, redevelopment of features etc).

 

Nic - Unfortunately, IE8 is a corporate requirement. I would love to go straight to IE11 but we have a lot of other web-based systems that would need to be tested / upgraded first - this would take a fair bit of time!

 

 

Back to the drawing board...


(Nic Hubbard) #5

And you tried turning off errors for the front end in the Global Prefs? I assume this won't help since Simple Edit isn't the front end, but still worth a shot.


(Byrn2lis) #6

Thanks Nic.

 

Even if errors could be turned off, I would want something to show the user of the error.