1 2 Previous Next 27 Replies Latest reply on Nov 22, 2007 4:18 AM by Adam Warski Go to original post
      • 15. Re: Plain skin
        Adam Warski Master

        Putting a custom class in the style class attribute does not work, as it is not the order of classes in this attribute that matters, but the order of < link > references to stylesheets. Read the CSS spec if you don't believe me.

        Also, from the beginning I wrote you that I want to have the styles in the *stylesheet*. Not in page code.

        And the whole problem, Mr. Magicians, comes from the fact that the < link >-s referring to RichFaces stylesheets sometimes are placed after, and sometimes before mine. Hence, the only way to get rid of the borders is to have the richfaces skin completely clear of any style.

        If you still don't understand my problem/ believe my problem, I'll be happy to conjure a sample program from my magical sleeve :).

        --
        Adam

        • 16. Re: Plain skin
          Sergey Smirnov Master

           

          "adamw" wrote:

          Also, from the beginning I wrote you that I want to have the styles in the *stylesheet*. Not in page code.


          Does not matter. Whatever you want.

          • 17. Re: Plain skin
            Sergey Smirnov Master

             

            "adamw" wrote:
            Putting a custom class in the style class attribute does not work, as it is not the order of classes in this attribute that matters, but the order of < link > references to stylesheets. Read the CSS spec if you don't believe me.


            The problem is not in the CSS spec. It is somewhere between the char and the keyboard.
            I guess you believe that the rules you define in your custom rich-stglpanel are overwritten by the similar rules defined by RichFaces in the same rich-stglpanel. Yes, the order is important in this situation, but RichFaces does not use rich-stglpanel at all. So, nothing can be overwritten in such way.


            • 18. Re: Plain skin
              Adam Warski Master

              The class .rich-stglpanel itself isn't overriden. But the panel header uses classes: .dr-stglpnl-h AND .rich-stglpanel. The first always defines a border, the second - as I wish. So if the border is displayed, depends on the precedence of .dr-stglpnl-h over .rich-stglpanel or the other way round. And this depends on the order of < link >-s, which differs.

              --
              Adam

              • 19. Re: Plain skin
                Sergey Smirnov Master

                do you have RichFaces filter off ?

                • 20. Re: Plain skin
                  Nick Belaevski Master

                  Adam,

                  Could you please provide some words on your environment?

                  Is it possible to obtain sample application? You can upload it somewhere or send it to nbelaevski at exadel d0t com . Thank you in advance!

                  • 21. Re: Plain skin
                    Adam Warski Master

                    Hello,

                    My environment is MacOSX 10.4 + firefox 2.0

                    A demo app can be downloaded here:
                    http://www.warski.org/richfaces_border_demo.tar.gz. It is a plain seam-gen app (with the lib directory removed, to reduce the size of the package from 5MB to 19KB :), so you'll have to add this and modify build.properties if you want to build&deploy), with urlrewritefilter added.

                    The first link on the home page leads to test.xhtml, and there is no border around the simple toggle panel, as specified in stylesheet/theme.css. The second link also leads to that page, but through a requestDispatcher.forward(test.xhtml) - and the border is there.

                    --
                    Adam

                    • 22. Re: Plain skin
                      Sergey Smirnov Master

                      The versions od the libs might make sense. Just print out the list of the file here.

                      • 23. Re: Plain skin
                        Adam Warski Master

                        There's quite a lot of those libs, and none has the version in their name. But they all come from seam 2.0.0.GA (if you just run seam-gen and create an empty project).

                        I've looked in seam's poms but can't see any version numbers. I suppose they used the latest ones.

                        --
                        Adam

                        • 24. Re: Plain skin
                          Adam Warski Master

                          So, anybody tried the demo app? :)

                          --
                          Adam

                          • 25. Re: Plain skin
                            Sergey Smirnov Master

                            in progress...

                            • 26. Re: Plain skin
                              Alexander Smirnov Master

                              Ok, I was found source of the your problem.
                              In case of the request processing by the urlRewriter filter, request forvarded to JSF pages by internal redirects. By default, server don't process other filters for internal redirects and includes, unless it specified by "dispatcher" directive in the filter mapping.
                              Your sample is worked fine with changed Seam filter mapping in the web.xml :

                              .........
                               <filter-mapping>
                               <filter-name>Seam Filter</filter-name>
                               <servlet-name>Faces Servlet</servlet-name>
                               <dispatcher>REQUEST</dispatcher>
                               <dispatcher>FORWARD</dispatcher>
                               <dispatcher>INCLUDE</dispatcher>
                               <dispatcher>ERROR</dispatcher>
                               </filter-mapping>
                              .......
                              


                              • 27. Re: Plain skin
                                Adam Warski Master

                                Hello,

                                thanks a lot! Now it seems logical that it didn't work.

                                It turns out I'm not a magician after all ;).

                                However, while skins are great in most situations, I would still advocate the need to have a completely empty skin available :).

                                --
                                Adam

                                1 2 Previous Next