3/13/2023 0 Comments Webtrees default page size![]() ![]() You are right that the body needs a default size, and that was the first thing I did. The reason that some parts might shrink is possibly the lack of a font-size declaration for the body. "Slightly", yes "completely", far from it! At any rate I guess I will do what I can to adjust the css to use ems where possible.įrom the sounds of it things will be slightly easier with 1.1.3 Your "simple" answer has one slight drawback-Even I sometimes for get that it is possible to zoom in the browser, LOL. The font-size declaration for the body tag should over-ride that changing em size but I'm no expert :) Browser size, I believe, defaults to having 1em = 16px and that default is changed when a user uses the zoom functionality of the browser. From the sounds of it things will be slightly easier with 1.1.3 but I will be happy enough if I can just make the most important parts a bit more accessible. ![]() I pretty much figured that there will be some places that I can't adjust via theme css or where I might have to adjust the px size rather than just converting to ems. That works with most browsers, and MACs have their own equivalent. There is one simple answer not on your list, which is to teach your users how to use CTRL +/- to zoom in and out of the screen plus CTRL 0 to reset it. This would not be a problem if you started with ems BEFORE designing the site, but trying to convert to it later is HARD. You will find many places where you end up with even smaller sizes than originally, simply because a holding div, within a div within a table within a div (etc) or something like that is proportionally reducing the ems automatically. The other problem with em measurements is the result of their cascading functionality. These will go eventually, but not in one go. We also still have many places that are overly complex places that use things like when or would be better. We're gradually removing them, but still have a way to go. That's is entirely written using px measurements, and many of its features really just can't function purely proportionally.Īlso, here are still many areas within the code that have hard-coded styling built into the core code, including font and dimensional changes. There are some really troublesome areas though, most notably our extensive use of jQuery. I "almost" got there with my site's theme. to have the only px font size be the one for the body and convert all the others to ems. Please Log in or Create an account to join the conversation. css to 16px and save it as name_large.css and have all of the fonts be automagically larger when a user selects "Brown Large" from the dropdown.Īnyone have any thoughts on those 2 options? Is there a 3rd/better option that I haven't thought of? Once I'm done with that I should be able to simply change the 13 px in the default's. ![]() Basically I have already started working on the default sub-theme's css to have the only px font size be the one for the body and convert all the others to ems. Implementing the second option is somewhat time consuming because it means going into the css and changing all the font sizes. I'm leaning towards option 2 for the simple reason that I don't want to add any more javascript onto the page. My eyes aren't getting any younger either :)Īs I see it there are 2 ways I can do this:ġ) Use some javascript to implement a dynamic font-size selector orĢ) Use the theme switching functionality in my custom theme's colors-based sub-theme selector to actually change stylesheets. I want to make it possible to use larger fonts for my users/visitors that may have trouble reading the default text sizes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |