HTML code help
-
Sorry to hear that. I was looking forward to the challenge in finding the answer!
<rant> I really dislike programmers who ignore the rest of the browsers. It's called standards, and of all the browsers, IE is the worst offender. In a world with iDevices, Androids you can't expect them to use IE, as it's not available!</rant>
-
@RoguePacket said:
@Dashrender Remove "background", and/or use "none" for that element (err, maybe "transparent" ).
replacing #717171 with none did fix this problem.
Thanks RP
-
@technobabble I'm right there with you. Unfortunately this EMR is probably 5 years old... they started when IE had the controls they felt they needed. Of course today we know that most if not all of them can be replaced with newer HTML 5 code.
The vendor claim to support Safari. This leaves me even more confused... why would the product work in Safari, but not FF or Chrome? some kind of back door deal between MS and Apple?
-
Weird as I understand it, webkit is what Safari, FF and Chrome are built with. I feel your pain and wish you good luck! Glad to see you got a fix!
-
@technobabble said:
Weird as I understand it, webkit is what Safari, FF and Chrome are built with. I feel your pain and wish you good luck! Glad to see you got a fix!
Safari is Webkit. IE is Trident. FF is Gecko and Chrome is just Chrome. Safari is the only main browser using Webkit today but lots of small projects use it but none that you would have heard of. Chrome used it to get started but left it some time ago. FF has never been anything but Gecko.
-
Webkit actually came from the KDE project. It was the basis for their browser systems.
-
Why not just try using the <hr> tag. It create a nice horizontal line and works on all browsers. It's very old school HTML. Been around a long time.
It works like like <br> there is no closing tag. http://www.w3schools.com/tags/tag_hr.asp
-
@Chamele0n said:
Why not just try using the <hr> tag. It create a nice horizontal line and works on all browsers. It's very old school HTML. Been around a long time.
It works like like <br> there is no closing tag. http://www.w3schools.com/tags/tag_hr.asp
aw, but it doesn't work any more on IE 10 or 11. I can't say if it works like the old way in FF or Chrome, etc.
<hr> had it's definition changed in HTML 5. While it will draw a line (sorta) it looks different than a plain o' black line. And for legal documents that's unacceptable.
The above CSS code with the background option changed to none has solved my issue.
-
HTML is not a format for legal documents
Also, you choose the standard. It's only HTML 5 on those new browsers if you make it that. Use XHTML 1.1 if you want.
-
@scottalanmiller said:
HTML is not a format for legal documents
Also, you choose the standard. It's only HTML 5 on those new browsers if you make it that. Use XHTML 1.1 if you want.
It's all outside my control.
The legal document side is the paper document created by the HTML - (maybe the vendor supports XHTML - who knows).
-
@scottalanmiller LOL, I was only correct about Safari. Reading what you said about FF an Chrome made me smh! Since there are times I have had to write CSS differently for FF and Chrome! Thanks for pointing out my misinformation!
-
@scottalanmiller said:
@technobabble....Chrome is just Chrome...
Chrome is using Blink since last year:
-
Ah ha, thanks. I've been a little out of touch as to web browsers the last few years. So Blink is Google's in house developed rendering engine.
MangoLassi runs on Google V8. That's what powers the entire site.
-
@RoguePacket said:
@scottalanmiller said:
@technobabble....Chrome is just Chrome...
Chrome is using Blink since last year:
Thanks for the links: It seems my retention for odd information but not remembering when it was relevant.
From the techcrunch article: "In an unusual move – and after a lot of back and forth between the KHTML team and Apple – Apple announced in 2005 that it would open source WebKit, and Google then adapted it for its Chrome browser. Interestingly, Google actually used a forked version of WebKit in the early days of Chromium but later reconciled its fork with the rest of the project."
-
The info is odd. Helps better define "browser issues". In this case it is more clearly seen as architectural decisions made earlier in the software development process.
Meanwhile, "Why can they all just get along?"
=:-o -
@RoguePacket said:
The info is odd. Helps better define "browser issues". In this case it is more clearly seen as architectural decisions made earlier in the software development process.
Meanwhile, "Why can they all just get along?"
=:-oCuz everyone wants to show off their new shiny toys and ideas first. HOWEVER I will say that IE is the worst offender. It's like they have never seen the W3C information.
-
Wonder if that was more a Ballmer thing (the guy of the "I will f@cking destroy those guys" fame)
Considering Netscape wasn't good enough so they made IE
Java wasn't good enough, so j#
C/C++ wasn't good enough, so C#
Flash wasn't good enough, so Silverlight -
@technobabble said:
Cuz everyone wants to show off their new shiny toys and ideas first. HOWEVER I will say that IE is the worst offender. It's like they have never seen the W3C information.
Well they actively didn't want to follow the W3C, at least not originally, because it didn't fit their vision. That is changing now as their vision failed, but that was the original intent.
-
@RoguePacket said:
Wonder if that was more a Ballmer thing (the guy of the "I will f@cking destroy those guys" fame)
Considering Netscape wasn't good enough so they made IE
Java wasn't good enough, so j#
C/C++ wasn't good enough, so C#
Flash wasn't good enough, so SilverlightNot that they weren't good enough, they just weren't proprietary. It was all an attempt to move people to Microsoft platforms.
-
Can't forget... they didn't want to use JavaScipt so they made JScript.
