We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 6726
    • 7,075 Posts
    I have come accross this strange thing : the h1#QE_Title quickedit style is conflicting with my pages style, but only in Firefox 1.5/Win. It doesn’t appear in Opera nor in IE huh

    here is the capture :



    The h1#QE_Title is a contextual style and should not be affected by the h1 style from my pages css, but it does. Probably a bug in Firefox’s engine, I can’t see why this problem should occur... Just thought I would share, see if anyone has come accross this too...

      .: COO - Commerce Guys - Community Driven Innovation :.


      MODx est l'outil id
      • 32847
      • 171 Posts
      Yes, I noticed the problem too, Quickedit title goes left with an indent rule on h1 in my css.
        • 1764
        • 680 Posts
        In the next release I’ll define some more CSS so this sort of thing won’t happen.

        There is an easy fix you can apply to your CSS though.
        The Toolbar HTML is always inserted right after the <body> tag so if you wrap your template in a div with a unique id (let’s say body_div) and then change your CSS to only apply to h1s within that div then none of your styles should affect the toolbar.

        #body_div h1 {
          [h1 styles go here]
        }
        


        The same thing can be done with other elements.
          • 6726
          • 7,075 Posts
          Thanks for confirming, Xeres.

          Adam, thanks for the solution.

          I have solved this changing h1 to h6 in
          assets\modules\quick_edit\output.class.inc.php on line 245

          <h1 id="QE_Title">{$_lang['QE_title']}</h1>


          Your solution is better though, I’ll switch back to it.



            .: COO - Commerce Guys - Community Driven Innovation :.


            MODx est l&#39;outil id
            • 13577
            • 302 Posts
            Quote from: aNoble at Jan 03, 2006, 12:40 PM

            In the next release I’ll define some more CSS so this sort of thing won’t happen...so if you wrap your template in a div with a unique id

            So am I correct in thinking that the QE will get the more specific CSS tags in the future? Because forcing the user to put their template in a <div id="something"> tag would be kind of a pain as then all meaningful styles, in order to maintain specificity, would have to be declared with #something in front of it.
              Standard Disclaimer
              I could be totally wrong.
              • 6726
              • 7,075 Posts
              I would say QE has pretty specific tags already. h1#QE_Title is pretty specific and the bug I reported has no reason other than faulty interpretation by Firefox (for once, it’s not IE...).

              You can still use h1 in your template’s CSS, I guess next FF release will fix that (let’s hope so...).
                .: COO - Commerce Guys - Community Driven Innovation :.


                MODx est l&#39;outil id
                • 32963
                • 1,732 Posts
                Quote from: davidm at Jan 04, 2006, 04:27 PM

                You can still use h1 in your template’s CSS, I guess next FF release will fix that (let’s hope so...).

                Did you report the error to the FF team?
                  xWisdom
                  www.xwisdomhtml.com
                  The fear of the Lord is the beginning of wisdom:
                  MODx Co-Founder - Create and do more with less.
                  • 6726
                  • 7,075 Posts
                  Didn’t have time to do so, but most certainly will !
                    .: COO - Commerce Guys - Community Driven Innovation :.


                    MODx est l&#39;outil id
                    • 13577
                    • 302 Posts
                    Quote from: davidm


                    Dang- did it again. You’re right of course. I’ll have to read the code and forum more carefully next time. I’ve had too many meetings today distracting me from the important stuff!
                      Standard Disclaimer
                      I could be totally wrong.
                      • 25663 MODX Staff
                      • 12,272 Posts
                      Try the following CSS file to see if it fixes the strange inheritance problems. I just ran into the same thing on the new MODx template!

                      It goes in assets/modules/quick_edit/styles/
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me