![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Hey team, long time no post! This is all because it got WILDLY BUSY in my life and then I forgot how to code (wait).
Anyway, with the latest code push (30 April 2019, or my 1 May 2019), custom styles no longer strip the viewport meta tag, meaning that it's possible to code mobile responsive layouts without need to check the box "Use layout's stylesheet(s)" in custom CSS.
However, any custom layout prior to 30 April 2019 that has the box unchecked still is not mobile responsive if they haven't already coded
media CSS into the stylesheets. But! This means that moving forward, everyone can, or those layouts can have code added to them to ensure that they are mobile responsive without need of a full rehaul.
What does this mean for my current layouts, because I use the checkbox hack to get them mobile responsive? At the moment nothing, because I have to do a full rehaul if anything. However, I'll look into a few things to see what I can do, but currently no promises only because of time.
I will be updating Basic Layout Coding Notes to reflect the updates in due time, because I want to mess around with testing the code first.
Meanwhile, some helpful links:
- Mobile responsive base project by
solarbird: found here, lend them a hand, it's good.
- Communities that already have mobile responsive layouts:
---
tofuhouse (heh)
---
myrtillenne
---
plainstyles
Also, hope you all enjoy the extra 50 icons, paid accounts! Cos I know I'm GONNA. 😏
PS: I will fix the Tectonic layouts though because of the new fixes, watch this space. Don't use these two layouts until I say so:
- perfect strangers
- blame it on me
Crisis averted! The bugs have been fixed by the team so layouts are usable again.
Anyway, with the latest code push (30 April 2019, or my 1 May 2019), custom styles no longer strip the viewport meta tag, meaning that it's possible to code mobile responsive layouts without need to check the box "Use layout's stylesheet(s)" in custom CSS.
However, any custom layout prior to 30 April 2019 that has the box unchecked still is not mobile responsive if they haven't already coded
![[profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
What does this mean for my current layouts, because I use the checkbox hack to get them mobile responsive? At the moment nothing, because I have to do a full rehaul if anything. However, I'll look into a few things to see what I can do, but currently no promises only because of time.
I will be updating Basic Layout Coding Notes to reflect the updates in due time, because I want to mess around with testing the code first.
Meanwhile, some helpful links:
- Mobile responsive base project by
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
- Communities that already have mobile responsive layouts:
---
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
---
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
---
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
Also, hope you all enjoy the extra 50 icons, paid accounts! Cos I know I'm GONNA. 😏
- perfect strangers
- blame it on me
Crisis averted! The bugs have been fixed by the team so layouts are usable again.
Tags: