Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] CSS regression #451

Open
peterstadler opened this issue Oct 15, 2024 · 8 comments
Open

[BUG] CSS regression #451

peterstadler opened this issue Oct 15, 2024 · 8 comments

Comments

@peterstadler
Copy link
Member

peterstadler commented Oct 15, 2024

Describe the problem

When reviewing the PR #445 with the clarinet quintet data it occurred to me that some CSS had changed. At first I blamed this PR but then I realized that it must have been introduced at some earlier stage since #444 also showed this behavior.

To Reproduce

Steps to reproduce the behavior:

  1. build Edirom Online from dev
  2. load clarinet data from pipeline build at https://git.uni-paderborn.de/wega/klarinettenquintett-edirom
  3. load both xar packages into a fresh existdb
  4. launch Edirom Online
  5. open "Editionsbericht"

Expected behavior

running with v1.0.0-beta.5
Bildschirmfoto 2024-10-15 um 10 10 17

how it looks like

running with current dev
Bildschirmfoto 2024-10-15 um 10 11 29

@bwbohl
Copy link
Member

bwbohl commented Oct 23, 2024

maybe it’s connected to the update of the TEI Stylesheets (#371 )?

@bwbohl
Copy link
Member

bwbohl commented Oct 23, 2024

Unfortunately I cannot reproduce this at the moment, all looks fine in my instance…

@daniel-jettka
Copy link
Contributor

daniel-jettka commented Oct 24, 2024

I can confirm the bug.

image

@daniel-jettka daniel-jettka removed their assignment Oct 24, 2024
@bwbohl
Copy link
Member

bwbohl commented Nov 7, 2024

Meanwhile I can confirm this, too…[EDIT]
No, I can’t…

I looked only at the heading sizes, not at the indentation!

Image

We should do a proper cleanup of resources/css/todo.css
Having it at all was a bad idea in the first place; it came into existence for quick css development but the rules defines should always be properly incorporated in the SASS definitions. Moreover, with the additional_css_path preference property it is easy to temporarily add any css file in the database for such purposes.

@peterstadler
Copy link
Member Author

There's a similar CSS issue in the Search window, see #463 (comment)

@daniel-jettka
Copy link
Contributor

I tried to fix the indentation. @peterstadler Could you check? I mean the heading looks different too... Is this a bigger thing or enough for now to change indentation?

@peterstadler
Copy link
Member Author

I think we need to investigate a bit more regarding the root cause of this change. I just compared the CSS files from the old and the current version: the old one loads a file /apps/weber-klarinettenquintett-eol-emeritus/resources/css/main.css, i.e. from the data collection, not from the Edirom Online collection. Hence, it seems to me that the loading of project specific CSS files fails somehow?!

@daniel-jettka daniel-jettka mentioned this issue Nov 27, 2024
1 task
@roewenstrunk
Copy link
Member

roewenstrunk commented Dec 2, 2024

In index.xql line 23

declare variable $editionUri := if($edition) then edition:findEdition($edition) else();
there should not be an if clause. You will always want to find the editionURI.

Then the project specific css is loaded again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

When branches are created from issues, their pull requests are automatically linked.

4 participants