css error

Basic support is open to all members of Volatyl Themes but what about those who need a little more? That's what Volatyl Themes subscriptions are for. The Priority Support subscription gets you more detailed, personal support while the Advanced Development subscription not only includes Priority Support, but also grants you access to premium content only seen by subscribers. This premium content will help you take your Volatyl websites to the next level with advanced development techniques, integration tips, and more information on how to really put Volatyl to use. Check out the subscriptions!

This topic is: not a support question

This topic contains 2 replies, has 3 voices, and was last updated by  benjamin 6 years ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #3801

    Roberto Porcar

    Hello, I found this minor issue:

    #main-content, #sidebars
    word-break: break-word;

    break-word seems to be a word-wrap value.

    valid word-break values are: normal|break-all|keep-all and inherit (i think).

    line 246, from style.css

    maybe it should be word-wrap: break-word; ?



    I think it can be EITHER:

    #main-content, #sidebars { word-break: normal; //or break-all | keep-all }


    #main-content, #sidebars { word-wrap: break-word; //or normal }


    Post count: 72

    Good catch, guys. Here’s what happened.

    word-break: break-word; is definitely a mistake. In Volatyl, it’s found on line 246. There, it targets #main-content and #sidebars.

    That’s definitely incorrect but here’s why it didn’t break anything.

    1. #main-content didn’t even need it. That was possibly me experimenting in the CSS and simply forgetting to go back and delete it.
    2. #sidebars gets the correct property and value later on at line 820. So that picked up line 246’s incorrect property and value for the sidebars.

    What I’m going to do is delete the entire CSS rule that you pointed out:

    #sidebars {
    	word-wrap: break-word;

    Because nothing is broken, though, I’ll wait to push this out with the next update.

    Good catch and thank you both for looking into it and posting!

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.