You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is option difficult to get a specific page to render as you would like. Often this can be overcome by tweaking the CSS. However, if you are not carefu you can change other pages that share elements with the same HTML class names. Being able to dynamically modify the template (e.g. with an id or class for the body or other HTML element) based on te current page would make it easier to make CSS tweaks without worrying about unseen side effects.
The text was updated successfully, but these errors were encountered:
The page_id could be used as the identifier of the page an then used as a pin that can be inserted as the id for the body tag of the template, e.g.
However, this would require modifying the ScreenProcessor to set a map for page_id using the screenid for the plugin and probably the dataset if set. It will also require modifying XHTML.pm to have a print:pin function so pins can be included within element attributes like for the body element above. This still will not full differentiate all page as any statically generated pages will still come back with the page_id static.
Further improvement may be needed for this dependent on how this new functionality is used.
It is option difficult to get a specific page to render as you would like. Often this can be overcome by tweaking the CSS. However, if you are not carefu you can change other pages that share elements with the same HTML class names. Being able to dynamically modify the template (e.g. with an id or class for the body or other HTML element) based on te current page would make it easier to make CSS tweaks without worrying about unseen side effects.
The text was updated successfully, but these errors were encountered: