[support] Errant chrome behavior and script probs

Tue May 27 22:13:12 UTC 2014

Check in the parent element and it should have a class added called 
contextual-links-region. That class adds a position:relative.

Jamie Holly
http://hollyit.net

On 5/27/2014 4:45 PM, Tony wrote:
> Difference when logged in is that this code gets inserted before 
> trigger-div:
>
> *<divclass="contextual-links-wrapper contextual-links-processed">*
> *<aclass="contextual-links-trigger"href="#">Configure</a>*
> *<ulclass="contextual-links">*
> *<liclass="block-configure first last">*
> *<ahref="/admin/structure/block/manage/slider_popup/slider_popup_block/configure?destination=homepanel">Configure 
> block</a>*
> *</li>*
> *</ul>*
> *</div>*
> <divclass="trigger-div">
> <a...
>
> Now to figure out what it does to the positioning.
>
>
> On Sun, May 25, 2014 at 7:58 PM, Jamie Holly 
> <hovercrafter at earthlink.net <mailto:hovercrafter at earthlink.net>> wrote:
>
>     <div class="trigger-div"><a class="trigger active" href="#">Useful
>     Links</a><p class="panel-orient">right</p><div class="panel"
>     style="top: -40px; padding-right: 228px; padding-left: 30px;
>     right: 0px; left: auto; margin-right: 118px; display: block;"><ul>
>         <li>
>             <h4>
>                 <a a="" href="http://polam.org/forms/WIRE_Form.pdf"
>     <http://polam.org/forms/WIRE_Form.pdf>>Outgoing wire form</a></h4>
>         </li>
>         <li>
>             <h4>
>                 <a a=""
>     href="http://polam.org/forms/IncomingForeign.pdf"
>     <http://polam.org/forms/IncomingForeign.pdf>>Incoming wire
>     form</a></h4>
>         </li>
>         <li>
>             <h4>
>                 <a a="" href="http://polam.org/rates/Loan_rates.pdf"
>     <http://polam.org/rates/Loan_rates.pdf>>Our Rates</a></h4>
>         </li>
>         <li>
>             <h4>
>                 <a a="" href="http://polam.org/docs/fees.pdf"
>     <http://polam.org/docs/fees.pdf>>Our Fees</a></h4>
>         </li>
>     </ul>
>     </div></div>
>
>
>     .trigger is just your link. You want .panel to position
>     absolutely, relative to it's parent element, which is
>     .trigger-div. The .trigger element is just another child of
>     .trigger-div, which doesn't send any rules to .trigger-div through
>     regular inheritance.
>
>     As far as it working for logged in users, I have no way of telling
>     without being logged in, but bare basic debugging in your
>     browser's tools should give you an idea of what is going on. Most
>     likely you have a stylesheet coming in only for logged in users
>     that is assigning relative to that division, or something close to
>     it, moving up the DOM hierarchy.
>
>     Jamie Holly
>     http://hollyit.net
>
>     On 5/25/2014 9:59 PM, Tony wrote:
>>     Bottom part already had relative on trigger. I added top:0 to
>>     panel class  No change
>>     But why does it behave differently when one signs in?
>>
>>
>>
>>     On Sun, May 25, 2014 at 12:51 PM, Jamie Holly
>>     <hovercrafter at earthlink.net <mailto:hovercrafter at earthlink.net>>
>>     wrote:
>>
>>         Update Chrome and see if the REM issue is fixed. They put a
>>         fix in on v34.
>>
>>         https://code.google.com/p/chromium/issues/detail?id=319623
>>
>>         If not, then this is always a good work around:
>>
>>         body > div {
>>             {set font-size rem here}
>>         }
>>
>>         For the bottom part, add position:relative to the
>>         trigger-div. If you want the panel to position at the top of
>>         that div, then you need to add a top:0 to the panel div as well.
>>
>>         Jamie Holly
>>         http://hollyit.net
>>
>>         On 5/25/2014 2:23 PM, Tony wrote:
>>>         Two things:
>>>
>>>           * Has anyone had experience or headaches with this issue:
>>>             http://stackoverflow.com/questions/20099844/chrome-not-respecting-rem-font-size-on-body-tag?
>>>             If so what solved it for you?
>>>           * My site polamdev.tony-mac.com
>>>             <http://polamdev.tony-mac.com> has a module in the
>>>             footer. Look for green button. Panel should slide out to
>>>             the left from the button but actually slides out at top
>>>             of page. BUT when I am logged in it behaves 'correctly'
>>>             and slides out next to div with green button. I have
>>>             looked and looked but see no permission problems, no css
>>>             problems, no script problems. What is different when I
>>>             am logged in, not knowing drupal that well? Any help
>>>             appreciated.
>>>
>>>         Thanks
>>>
>>>         Tony
>>>
>>>
>>>         -- 
>>>
>>>         */Anthony Stefan Maciejowski/*
>>>
>>>         */http://about.me/TonyMac <http://www.about.me/TonyMac>/*
>>>
>>>
>>>
>>>
>>
>>
>>         --
>>         [ Drupal support list | http://lists.drupal.org/ ]
>>
>>
>>
>>
>>     -- 
>>
>>     */Anthony Stefan Maciejowski/*
>>
>>     */http://about.me/TonyMac <http://www.about.me/TonyMac>/*
>>
>>
>>
>>
>
>
>     --
>     [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
>
> -- 
>
> */Anthony Stefan Maciejowski/*
>
> */http://about.me/TonyMac <http://www.about.me/TonyMac>/*
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20140527/769b5ea1/attachment.html 