Maintaining Feature Settings for Page Title Block Across All Regions

Also, could you add an option to center the title, I add style through CSS injector to center the title. Whenever the page is refreshed, the title is first left aligned and then centered, which gives a strange feeling.

Hello,

I updated the dev version → so that if you move or add a new page title block to any region, you will still be able to use all the feature settings for the page title. This feature was on my radar because it is useful in some layouts, and I received several requests in the past asking if the page title could be moved to any region.

Note: In the Solo theme, to view region settings, some blocks must be enabled or disabled in the respective region.

Best wishes,
Alaa

Thank you very much for the response.

I currently have an issue with the CSS injector. When using a custom CSS style to override the default style, whenever the page is refreshed, it always executes the default style first and then the custom style. For example, the title is left aligned by default. When I set the title to center through the CSS injector, whenever the page is refreshed, the title is first left aligned and then jumps to center.

Is there a solution to this problem? Thank you

Hello,

I forgot to mention that I added a checkbox to center the page title. You should see this option available now. For the problem you mentioned, please share the code you are using to center the page title, and I'll take a look.

Best wishes,
Alaa

I have found the reason now, I set the title to be centered on the mobile version, while the desktop version is left by default. When browsing pages on the mobile and flushing, it first show the default CSS style of the desktop, and then show the style of the mobile, There is a delay in browsing on the phone, so will see a jumping effect.

.chrome.mobile h1.page-title-text{text-align:center;}

It may be due to the module browserclass → use .chrome.mobile, it at the last using JavaScript to add the class.

Thank you

Automatically closed - issue fixed for 2 weeks with no activity.