github / github/browser-support
Github action views deliver less content to Firefox and Chrome than Safari
- Langage dominant
- JavaScript
- Étoiles
- 165
- Forks
- 43
- Merge moyen
- 1 j 18 h
- PR mergées (30 j)
- 2
Description
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
Requested labels: org-9343010-{{ arch }}-k8s
```
## 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:
```
... 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?
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start by reproducing the linked GitHub Actions job on macOS in Safari, Firefox, and Chrome, then compare the log DOM with Firefox on Ubuntu. Investigate why the log container is empty only in Firefox and Chrome on macOS. Done means identifying a reproducible browser-support cause and documenting or fixing the behavior with cross-browser verification.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100