ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    HTML code help

    Scheduled Pinned Locked Moved IT Discussion
    42 Posts 6 Posters 8.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DashrenderD
      Dashrender @technobabble
      last edited by

      @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?

      1 Reply Last reply Reply Quote 0
      • T
        technobabble
        last edited by

        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!

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @technobabble
          last edited by

          @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.

          T RoguePacketR 2 Replies Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller
            last edited by

            Webkit actually came from the KDE project. It was the basis for their browser systems.

            1 Reply Last reply Reply Quote 0
            • Chamele0nC
              Chamele0n
              last edited by Chamele0n

              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

              DashrenderD 1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @Chamele0n
                last edited by

                @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.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  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.

                  DashrenderD 1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @scottalanmiller
                    last edited by

                    @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).

                    1 Reply Last reply Reply Quote 0
                    • T
                      technobabble @scottalanmiller
                      last edited by

                      @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!

                      1 Reply Last reply Reply Quote 0
                      • RoguePacketR
                        RoguePacket @scottalanmiller
                        last edited by

                        @scottalanmiller said:
                        @technobabble

                        ....Chrome is just Chrome...

                        Chrome is using Blink since last year:

                        • http://en.wikipedia.org/wiki/Blink_(layout_engine)
                        • http://en.wikipedia.org/wiki/Web_browser_engine
                        • Also, http://techcrunch.com/2013/04/03/google-forks-webkit-and-launches-blink-its-own-rendering-engine-that-will-soon-power-chrome-and-chromeos/
                        T 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller
                          last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • T
                            technobabble @RoguePacket
                            last edited by

                            @RoguePacket said:

                            @scottalanmiller said:
                            @technobabble

                            ....Chrome is just Chrome...

                            Chrome is using Blink since last year:

                            • http://en.wikipedia.org/wiki/Blink_(layout_engine)
                            • http://en.wikipedia.org/wiki/Web_browser_engine
                            • Also, http://techcrunch.com/2013/04/03/google-forks-webkit-and-launches-blink-its-own-rendering-engine-that-will-soon-power-chrome-and-chromeos/

                            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."

                            1 Reply Last reply Reply Quote 0
                            • RoguePacketR
                              RoguePacket
                              last edited by RoguePacket

                              @technobabble

                              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

                              T 1 Reply Last reply Reply Quote 0
                              • T
                                technobabble @RoguePacket
                                last edited by

                                @RoguePacket said:

                                @technobabble

                                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

                                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.

                                RoguePacketR scottalanmillerS 2 Replies Last reply Reply Quote 0
                                • RoguePacketR
                                  RoguePacket @technobabble
                                  last edited by

                                  @technobabble

                                  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

                                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller @technobabble
                                    last edited by

                                    @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.

                                    1 Reply Last reply Reply Quote 0
                                    • scottalanmillerS
                                      scottalanmiller @RoguePacket
                                      last edited by

                                      @RoguePacket said:

                                      @technobabble

                                      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

                                      Not that they weren't good enough, they just weren't proprietary. It was all an attempt to move people to Microsoft platforms.

                                      1 Reply Last reply Reply Quote 1
                                      • scottalanmillerS
                                        scottalanmiller
                                        last edited by

                                        Can't forget... they didn't want to use JavaScipt so they made JScript.

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          technobabble
                                          last edited by

                                          Too true and although there are many MS things along the way I have liked, most of what you mentioned was wasted time on programming much like Office Accounting. MS giveth and MS taketh away. Look for my upcoming RANTs on MS OneNote and Outlook 365.

                                          scottalanmillerS 1 Reply Last reply Reply Quote 2
                                          • scottalanmillerS
                                            scottalanmiller
                                            last edited by

                                            J++ was the original replacement to Java. It was just a really crappy version of Java. I had a Visual J++ kit once up on a time.

                                            J++ was replaced by J# in 2004 which kept the Java syntax but switched from Java VM underneath to the .NET system. Making it "easy" for Java people to move over to the .NET world.

                                            But that too was discontinued in 2006 as C# itself was always a Java replacement, not targeted at C/C++ but at Java. Java is a C derivative in syntax as is C#, so in a way it's all C, sort of, but conceptually Java and .NET are pretty far removed. C# goes after Java though, not C. Microsoft maintains Visual C++ as their C/C++ replacement.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post