issue_comments

Table actions

4 rows where issue = 588526556 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

author_association 2

issue 1

  • html repr does not work in Edge browser · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1114711569 https://github.com/pydata/xarray/issues/3898#issuecomment-1114711569 https://api.github.com/repos/pydata/xarray/issues/3898 IC_kwDOAMm_X85CcSYR stale[bot] 26384082 2022-05-02T10:37:47Z 2022-05-02T10:37:47Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr does not work in Edge browser 588526556
604854297 https://github.com/pydata/xarray/issues/3898#issuecomment-604854297 https://api.github.com/repos/pydata/xarray/issues/3898 MDEyOklzc3VlQ29tbWVudDYwNDg1NDI5Nw== benbovy 4160723 2020-03-27T07:26:28Z 2020-03-27T07:38:38Z MEMBER

I know we use some relatively new CSS features to get the HTML repr working

display: grid and display: contents are the two newest features used in the repr I think. display: grid seems well supported in Edge , but display: contents might not be well supported in old versions of Edge?

Unfortunately, I don't think there is an easy workaround to avoid display: contents (given that there is even less support for subgrid).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr does not work in Edge browser 588526556
604592266 https://github.com/pydata/xarray/issues/3898#issuecomment-604592266 https://api.github.com/repos/pydata/xarray/issues/3898 MDEyOklzc3VlQ29tbWVudDYwNDU5MjI2Ng== blaylockbk 6249613 2020-03-26T18:14:02Z 2020-03-26T18:14:02Z NONE

Oh yes, forgot to mention...I'm stuck with the non-chromium version of Edge 44.18362.449.0. (It's a work computer and don't have much browser freedom).

I just tested it on my personal computer (Edge 80.0.361.69) and the html repr works there.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr does not work in Edge browser 588526556
604551386 https://github.com/pydata/xarray/issues/3898#issuecomment-604551386 https://api.github.com/repos/pydata/xarray/issues/3898 MDEyOklzc3VlQ29tbWVudDYwNDU1MTM4Ng== shoyer 1217238 2020-03-26T17:04:25Z 2020-03-26T17:04:25Z MEMBER

Thanks for the report!

I know we use some relatively new CSS features to get the HTML repr working, but our intent is definitely for this to work across as many platforms as possible, not just Chrome. I'll double check, but I'm pretty sure the HTML repr works in recent versions of Firefox, too.

Which version of Edge are you using? My understanding was that newer versions of Edge are baed on Chromium (the rendering engine from Chrome).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr does not work in Edge browser 588526556

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);