Fields Hints are not hiding after being selected

[kelvinmandlik]

This issue pertains to the following package(s):

• GraphQL Playground - Electron App
• GraphQL Playground HTML
• GraphQL Playground
• GraphQL Playground Express Middleware
• GraphQL Playground Hapi Middleware
• GraphQL Playground Koa Middleware
• GraphQL Playground Lambda Middleware

What OS and OS version are you experiencing the issue(s) on?

• Happening on every OS. Run in Windows, Linux, Arch

What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?

I am using rust packages

• actix-web = "4.8.0"
• juniper = "0.16.1"
• juniper_actix = "0.6.0"

But it's not only happening in rust It's also happening in nodejs package as well. It is seen that the issue is happening after the recent update of graphql or playground. In nodejs previously it was not happening.

What is the expected behavior?

• It should get hidden after being selected

What is the actual behavior?

• Tips are staying on the UI after refresh it hides

What steps may we take to reproduce the behavior?

• Just write down the query or mutation it will show the tips and once selected it will stay on UI

Please provide a gif or image of the issue for a quicker response/fix.

[asahi-kawajiri]

I've faced same issue. (x_x )/

[kelvinmandlik]

@asahi-kawajiri Did you find any solution or atleast workaround?

[iatanas0v]

For now you can use Firefox, the issue is related to Chrome deprecating DOMNodeRemoved mutation event

[JoaoBGusmao]

See graphql/graphql-playground#1429 (comment)

[scaraux]

I made a fix for it : graphql/graphql-playground#1431 @kelvinmandlik

[vinhnglx]

When do we merge this fix? For now, either Safari or Firefox will help. Chrome or Edge will face the same issue.

[JoaoBGusmao]

When do we merge this fix? For now, either Safari or Firefox will help. Chrome or Edge will face the same issue.

@vinhnglx I don't believe a fix will ever get merged. It is an abandoned project. If you cannot switch to another Graphql IDE, your best option is to fork, apply a fix and publish it just like I did.
I'm using this playground from a Google Chrome extension, so I published my fork to Chrome Store, here is the link if anyone needs a working Chrome extension.

[acao]

hello all. you may recall the creator of graphql-playground and I authored an article several years ago about how playground was to be deprecated for graphiql. we are well underway with this effort, and we reccomend switching an building plugins for additional functionality

the issues you are reporting here are related to our library codemirror-graphql, not playground itself