[Pro] Solving disclosure triangle conundrum

have a look at this page: Test Page - MaxWithCSSMenuAction

Interestingly, while the triangles rotate fine in Safari 5.1.10 the styling for the drop downs falls apart.

Must have a closer look.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Must be missing something from the CSS that I linked up using a base href tag. Was that screenshot of my page? What happens if you force-refresh?

Walter

On Apr 4, 2015, at 1:04 PM, DeltaDave email@hidden wrote:

have a look at this page: Test Page - MaxWithCSSMenuAction

Interestingly, while the triangles rotate fine in Safari 5.1.10 the styling for the drop downs falls apart.

Must have a closer look.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Must be missing something from the CSS that I linked up using a base href tag. Was that screenshot of my page? What happens if you force-refresh?

Yes that was your page but it looks fine in Chrome 37 and not showing any missing resources in the web Inspector.

However on closer look testpage-css-menu.css shows as empty in Safari 5.1.10

Go figure!?

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Is it possible that the invalid type-weight declaration in the first line of that CSS file is throwing things off for that version of Safari?

body { color:#464651; font-family:'Open Sans', sans-serif;; font-size:15px; line-height:1.4; text-align:left; margin-top:0px; margin-bottom:5px; type-weight:400; margin:0px; background-color:#b4b4b4; height:100% }

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That could be it. Also note the double-semicolons in there. I think this is the trigger.

Walter

On Apr 4, 2015, at 1:23 PM, DeltaDave email@hidden wrote:

Is it possible that the invalid type-weight declaration in the first line of that CSS file is throwing things off for that version of Safari?

body { color:#464651; font-family:'Open Sans', sans-serif;; font-size:15px; line-height:1.4; text-align:left; margin-top:0px; margin-bottom:5px; type-weight:400; margin:0px; background-color:#b4b4b4; height:100% }

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Also note the double-semicolons in there. I think this is the trigger.

So Peter you will need to check any styles that you have added extended attributes to and check for errors like this.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I have used the type weights (700 and 400) used by Google, as the font has seven weights (100, 200, etc.). Please advise on how to correctly spec type weights. Freeway seems to recognize it and handle it as intended.

As to the extra colon, I think it came from adding a colon at the end of the font set specification. I removed it.

I can’t find the line of code to which you refer on the page so I assume it is in the site’s Style Sheet. How to I view that code using the Developer menu in Safari?

Refreshing your page, Walter, in Safari 8.0.4, I am now getting what DeltaDave shows. Did you change something in that code? I replaced the semicolon in the font set, to see if my removal of it provoked this, to no avail.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I cloned your page, and I haven’t updated my clone, so that’s what you’re seeing. As to the type weight, the point that Dave was making was that you used the code type-weight, when the actual code is font-weight. So change that, and your page should be good.

Walter

On Apr 4, 2015, at 2:03 PM, Peter Laundy email@hidden wrote:

I have used the type weights (700 and 400) used by Google, as the font has seven weights (100, 200, etc.). Please advise on how to correctly spec type weights. Freeway seems to recognize it and handle it as intended.

As to the extra colon, I think it came from adding a colon at the end of the font set specification. I removed it.

I can’t find the line of code to which you refer on the page so I assume it is in the site’s Style Sheet. How to I view that code using the Developer menu in Safari?

Refreshing your page, Walter, in Safari 8.0.4, I am now getting what DeltaDave shows. Did you change something in that code? I replaced the semicolon in the font set, to see if my removal of it provoked this, to no avail.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I see the problem with my example now – you took down the original test page, and with it went all of the linked CSS. I didn’t cache that here, I just put a base href at the top of my page to point back to your stylesheet. So my example is now lost to the ages.

Walter

On Apr 4, 2015, at 2:03 PM, Peter Laundy email@hidden wrote:

I have used the type weights (700 and 400) used by Google, as the font has seven weights (100, 200, etc.). Please advise on how to correctly spec type weights. Freeway seems to recognize it and handle it as intended.

As to the extra colon, I think it came from adding a colon at the end of the font set specification. I removed it.

I can’t find the line of code to which you refer on the page so I assume it is in the site’s Style Sheet. How to I view that code using the Developer menu in Safari?

Refreshing your page, Walter, in Safari 8.0.4, I am now getting what DeltaDave shows. Did you change something in that code? I replaced the semicolon in the font set, to see if my removal of it provoked this, to no avail.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I can’t find the line of code to which you refer on the page so I assume it is in the site’s Style Sheet.

I would look at the Style inspector and Edit the body style

I think that you will find the type-weight declaration in the Extended section of that.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I see the problem with my example now — you took down the original test page, and with it went all of the linked CSS. I didn’t cache that here, I just put a base href at the top of my page to point back to your stylesheet. So my example is now lost to the ages.

Didn’t intend to obliterate your excellent example! I have now put back up the page, with the unicode triangles removed, fixes to the double semicolon and the font-weight specification, and links to other pages in the site build removed.

This doesn’t seem to be having any impact on your page though: it continues to show the previous version of the page.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options