Protesilaos Stavrou <i...@protesilaos.com> writes: >> This is not an exhaustive list. We have a number of markup objects that >> are fontified overriding the containing element/paragraph/heading face: >> >> - target links >> - timestamps >> - footnotes >> - radio targets >> - macros >> - inline export snippets >> >> I am not 100% sure we should unconditionally prepend their faces to >> the containing headline/table/etc. >> >> CCing Protesilaos. This discussion might be of interest for him. > > I think it makes sense to not override the background because otherwise > the heading can look visually "broken". See attached screenshot for an > example: it is called "demo-org-heading-with-background.png". In that > screenshot I include an overline for the heading, to show how this is > not limited to the background colour but extends to all face attributes. > To this end, I also attach "demo-org-heading-with-more-height.png" which > shows how the date is not scaling to match the heading's increased text > height.
I agree that override (what we do now) is clearly not good. The question, however, is whether we should prioritize object face over the containing element face or vice versa: Should link properties take precedence over headline or should headline properties take precedence? For example, if link explicitly sets face height to be smaller, should we honor it? Or should we honor the headline face height, if set? Similar for background. In your example, the white background override does not really look nice when heading has its own background. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
