You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the issue on a private repository, which does not show the clockify widget, the HTML is considerably different from that on the page which has a working clockify widget!
I took a look at the HTML on the two pages to see if there's an obvious reason the controls aren't inserted, and there is!
Example of a non-working page (from an issue in one of our company internal repositories) (can't share entire URL since it wouldn't work for external people, but it's not on a custom domain or anything; it has the form https://github.com/CompanyName/repository_name/issues/12345 and the clockify widget used to work here):
I have reformatted the HTML since as delivered by github it's all on one line:
Here's an example of the "gh-header-show" div (inside which the button appears) from a working page (from a clockify issue!) at #280 ... again I reformatted for legibility, but the delivered HTML was already a bit formatted / indented, on delivery, here.
It's not immediately clear to me what an appropriate fix here would be ... insert the clockify elements after the div which has the attribute data-component="TitleArea" or simply do a similar append into the div with attribute data-testid="issue-header" or maybe aria-label="Header"? I believe this would put it in the right place ... but feels fragile. Maybe no less fragile than the existing method, which is now broken for me!!
Over to you for thoughts, Clockify developers!
Quick pic of the folded HTML ... I imagine that the two clockify controls should be added to the list of three divs shown here:
The text was updated successfully, but these errors were encountered:
I tried inserting it in data-component="PH_Title" by copying insert for '.gh-header-actions:not(.clockify)', and replacing it with 'div[data-component="PH_Actions"]:not(.clockify)', and it works fine. I did not have time to check how to extract issue id and title.
One more note this is probably related to new feature of parent and subissues in github. That feature is still in beta so not sure will this fix work when features is fully released.
The key difference here:
I took a look at the HTML on the two pages to see if there's an obvious reason the controls aren't inserted, and there is!
Clearly the heuristic by which the clockify extension injects the button and time field into the page no longer recognises this div as the location in which it needs to be placed, since the
gh-header-actions
class is not used here on the problem page!Example of a non-working page (from an issue in one of our company internal repositories) (can't share entire URL since it wouldn't work for external people, but it's not on a custom domain or anything; it has the form
https://github.com/CompanyName/repository_name/issues/12345
and the clockify widget used to work here):I have reformatted the HTML since as delivered by github it's all on one line:
Here's an example of the "gh-header-show" div (inside which the button appears) from a working page (from a clockify issue!) at #280 ... again I reformatted for legibility, but the delivered HTML was already a bit formatted / indented, on delivery, here.
It's not immediately clear to me what an appropriate fix here would be ... insert the clockify elements after the div which has the attribute
data-component="TitleArea"
or simply do a similarappend
into the div with attributedata-testid="issue-header"
or maybearia-label="Header"
? I believe this would put it in the right place ... but feels fragile. Maybe no less fragile than the existing method, which is now broken for me!!Over to you for thoughts, Clockify developers!
Quick pic of the folded HTML ... I imagine that the two clockify controls should be added to the list of three divs shown here:
The text was updated successfully, but these errors were encountered: