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

single page report is too wide #2336

Closed
eitzenbe opened this issue Dec 10, 2020 · 3 comments
Closed

single page report is too wide #2336

eitzenbe opened this issue Dec 10, 2020 · 3 comments

Comments

@eitzenbe
Copy link
Contributor

eitzenbe commented Dec 10, 2020

When failure information is too large, the table expands making the header section appear to be hidden right side out of screen.

To work around the following two css should be added (maybe configurable?)

.compact-wrapper {
    max-width: 1200px;
}
.for-failure {
    max-width: 1150px;
    line-break: anywhere;
}

if the scnarioName column could be resized to max 30 or 40% the display would be nice even for very large failure details.
Currently this column is width fixed by hardcoded style value so no way to mingle around here :(

@eitzenbe
Copy link
Contributor Author

In order to fix this within a mvn build:

<plugin>
        <groupId>com.google.code.maven-replacer-plugin</groupId>
        <artifactId>replacer</artifactId>
        <version>1.5.3</version>
        <executions>
          <execution>
            <phase>post-integration-test</phase>
            <goals>
              <goal>replace</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <file>target/site/serenity/serenity-summary.html</file>
          <replacements>
            <replacement>
              <token>&lt;/head&gt;
              </token>
              <value>&lt;style&gt;.compact-wrapper {
                max-width: 1200px;
                }

                .for-failure {
                max-width: 1150px;
                line-break: anywhere;
                }&lt;/style&gt;&lt;/head&gt;
              </value>
            </replacement>
          </replacements>
        </configuration>
      </plugin>

@wakaleo
Copy link
Member

wakaleo commented Dec 10, 2020

Is there any reason why this change shouldn't be permanent?

@eitzenbe
Copy link
Contributor Author

well people with HDPI Monitors might want to have different value ;) or some might even preferr 1024

@wakaleo wakaleo closed this as completed Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants