Wow - that has lost me HOURS in the past (about 6 hours if I remember
correctly). A designer decided to attach a style to the Form tag - big no
no.
I remember trawling through a custom stylesheet trying to narrow the cause
down and it was a style on the form tag.
This usually happens because designers are ignorant of ASP.NET - ie. they
are not aware that nested directly below the Body tag we need a Form tag
with runat="server" to make the page work in ASP.NET and so server controls
work.
So, instead of wrapping their cut-up/design in one form
tag immediately below the Body tag they instead use Form tags within the
page for something like the search box, or for a custom form in the cut-up.
They then add styles to the Form tag in their CSS so they can style that
specific element....
You then implement this cut-up in SharePoint (or any ASP.NET master page in
fact) and you get weird stuff happening !!!
The biggest problem is trying to explain this all to a designer, it goes
straight over their heads - they deny any wrongdoing and just blame
SharePoint.
Sezai
On Tue, Nov 18, 2008 at 7:07 AM, ken zheng <[EMAIL PROTECTED]> wrote:
> Hi Guys:
>
> Thanks for all the help, finally I found that's because
> html form {
> height:100%;
> }
>
> in the style sheet cause the problem. Once I commented out, the paly
> buttons appear.
>
> Cheers
>
> Ken
>
> ------------------------------
> From: [EMAIL PROTECTED]
> To: [email protected]
> Date: Mon, 17 Nov 2008 14:45:38 +0900
>
> Subject: RE: [OzMOSS] RE: [listserver] (No Subject)
>
> Okay.
>
> Hm...let's use Reflector to see what that Apply CSS does to your site. I'm
> afraid it's setting up a particular property that is used by your
> page/control that then causes problems with the picture library web-part.
>
> Have you checked that the styles in your custom style sheet are custom (ie.
> you're not overriding OOTB classes)? And if you are overriding any OOTB
> class, have you checked that you haven't set the visibility into hidden?
> Setting a control into hidden mode will only cause problem because the HTML
> ID may be used/referenced by other controls.
>
> Apart from that I can't think of anything else of why this problem occurs.
> I always do branding and never had this problem before.
>
> Cheers,
> Tommy
>
> ------------------------------
> *From:* [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of ken
> zheng [EMAIL PROTECTED]
> *Sent:* Monday, 17 November 2008 2:40 PM
> *To:* [email protected]
> *Subject:* RE: [OzMOSS] RE: [listserver] (No Subject)
>
> Tommy:
>
> The page still contains core.css and customized css
>
> <link rel="stylesheet" type="text/css"
> href="/_layouts/1033/styles/core.css?rev=5msmprmeONfN6lJ3wtbAlA%3D%3D"/>
> <link rel="stylesheet" type="text/css"
> href="/_layouts/1033/Styles/custom_white.css"/>
>
> Ken
> ------------------------------
>
> From: [EMAIL PROTECTED]
> To: [email protected]
> Date: Mon, 17 Nov 2008 14:29:18 +0900
> Subject: RE: [OzMOSS] RE: [listserver] (No Subject)
>
>
> OK I'm afraid that since it's a .NET control it will render a different
> text if you set the master page using GUI if you know what I mean. Since now
> you switch the master page then that control will render your custom CSS but
> not the CORE.CSS. The best way to check what's renderd is by go to browser
> -> View Source then you can see if CORE.CSS is still referenced by your
> page.
>
> I personally wouldn't recommend you doing it. I will normally have another
> reference on my master page to go to my custom CSS and I will you master
> page switcher instead of CSS switcher.
>
> Cheers,
> Tommy
>
> ------------------------------
> *From:* [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of ken
> zheng [EMAIL PROTECTED]
> *Sent:* Monday, 17 November 2008 2:24 PM
> *To:* [email protected]
> *Subject:* RE: [OzMOSS] RE: [listserver] (No Subject)
>
> Hi Tommy:
>
> We actualy select customized css from
> "Specify a CSS file to be used by this publishing site and all sites that
> inherit from it", but in the master page we do have "<SharePoint:CssLink
> runat="server"/>" in the HEAD
>
> Cheers
>
> Ken
>
>
> ------------------------------
>
> From: [EMAIL PROTECTED]
> To: [email protected]
> Date: Mon, 17 Nov 2008 16:10:26 +1100
> Subject: [OzMOSS] RE: [listserver] (No Subject)
>
>
> Tommy that's a good point which not a lot of people realise.
>
>
>
> They don't call them *cascading* stylesheets for nothing. J
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf
> Of *Tommy Segoro
> *Sent:* Monday, 17 November 2008 3:40 PM
> *To:* [email protected]
> *Subject:* [OzMOSS] RE: [listserver] (No Subject)
>
>
>
> Do you still reference the CORE.CSS or do you completely remove it from the
> <HEAD> tag? You should put your custom CSS *after* the CORE.CSS.
>
>
>
> eg
>
> <HEAD>
>
> * <**Sharepoint**:**CssLink** ID="CssLink1" runat="server"/>*
>
> <link rel="stylesheet" href="/mycustomcss.css" />
>
>
>
> Something like that.
>
>
>
> This way you will not remove the needed CSS classes from CORE.CSS. You can
> also override OOTB CSS class names in your custom CSS.
>
>
>
> Tommy
>
>
> ------------------------------
>
> *From:* [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of ken
> zheng [EMAIL PROTECTED]
> *Sent:* Monday, 17 November 2008 1:32 PM
> *To:* [email protected]
> *Subject:* [listserver] (No Subject)
>
> Hi Guys:
>
> The SharePoint site does not display the buttons on the slideshow popup
> window that displays when you the picture library and select View Slide Show
> from the actions menu. I know the issue is caused by my customized styles
> sheet. after i reset back the styles sheets to default CORE.CSS, it works.
>
> So anybody knows where should I notice in css file?
>
> Cheers
>
> Ken -------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by mailenable.com
>
> -------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by mailenable.com
> -------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by
> mailenable.com-------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by mailenable.com
> -------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by
> mailenable.com-------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by mailenable.com
> -------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by mailenable.com
> -------------------------------------------------------------------
> OzMOSS.com - to unsubscribe from this list, send a message back to the list
> with 'unsubscribe' as the subject.
> Powered by mailenable.com
>
------------------------------------------------------------------- OzMOSS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered by mailenable.com
