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

Github action views deliver less content to Firefox and Chrome than Safari #55

Open
ericpromislow opened this issue Jun 11, 2024 · 0 comments

Comments

@ericpromislow
Copy link

ericpromislow commented Jun 11, 2024

This is probably the wrong repo, but I'm at a loss, and have to use safari now.

Trying to view the results of https://github.com/rancher/webhook/actions/runs/9473749556/job/26101987673 I can see 3 lines in Safari at the start of the run, including the syntax error in the runner which is why the job is permanently queued. But I don't see those lines in either Firefox or Chrome (all on macOS), do see them on Firefox on Ubuntu.

Safari (no bug):

Using the browser extensions, in Safari the key elements are:

div: class="uxr_CheckRun-header CheckRun-header mb-2 d-flex flex-justify-between flex-items-center mb-1 py-3 pr-3 js-checks-log-toolbar rounded-top-0 rounded-md-top-1 pl-3 pl-md-4"

nextSibling:
div: class="position-relative js-full-logs-container WorkflowRunLogsScroll"

child:
div: class="text-mono text-small py-1 my-2 mx-2 js-check-run-log-display-container"

child: 
bunch of divs and spans leading to text like
<span class="" style=""><!----><!----><!----><!----><!---->Requested labels: org-9343010-{{ arch }}-k8s
<!----><!----><!----></span>

In Firefox, I see this instead:

div: uxr_CheckRun-header CheckRun-header mb-2 d-flex flex-justify-between flex-items-center mb-1 py-3 pr-3 js-checks-log-toolbar rounded-top-0 rounded-md-top-1 pl-3 pl-md-4

nextSibling:
div: position-relative js-full-logs-container WorkflowRunLogsScroll

child:
div: js-check-run-log-display

child:
<div class="text-mono text-small py-1 my-2 mx-2 js-check-run-log-display-container">
            </div>

... notice the empty element

Chrome:

I get the same behavior happening on Chrome.

This might be a case of "doesn't work on my machine". I see the helpful text on ubuntu/firefox.

I'm not running any extensions that mess with the DOM.

Any ideas?

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

1 participant