Hi Ernest,
That’s not a problem, as I have other ways to work around this. I don’t think I would have wanted to complicate this with separate JS. It’s preferable to have this all controlled from the single filter. So even if you were willing to do that work I wouldn’t have wanted to make it more complex.
What I’m probably going to do here is use your server-side mobile detection in combination with a smaller font-size starting at 768px. This way those in-between screen sizes are taken care of. Up until now I’ve had only the one title font-size in place for all screen sizes. I’ll just make a smaller font-size to help alleviate this problem.
Btw, I actually have my own outsourced team of developers that I already work with. But suffice to say those hours are very expensive. This is why I appreciate your help so much.
My thanks again for all your help developing this filter. I look forward to showing you everything in a few more weeks.
I’ll keep an eye out on your next updates for everything else we covered in this thread.
P.S. I have installed the mobile detection option and tweaked my responsive css to work well with it. I thought you’d like to know that the mobile detection does in fact work in Chrome’s emulator. I also found that the mobile detection is including tablets like iPads (so it is not limited to phones). This meant I was able to keep a slightly larger font-size for those devices since the lower word limit applied. The only thing I have left to do is test this on the real devices, which I will do after the next deployment. This is all working quite nicely. Thank you Ernest! =)
All my best,
~ Michael