Skip to content

Handle loss of WebGL context #375

@wouterlucas

Description

@wouterlucas

Seems newer Chrome >123 versions will pull the WebGL context, this was raised in a previous L2 issue where we stated coming up with such a solution would be hard with the state of the L2 code being what it is. However we should experiment with ways to do so in L3.

Assuming:

  • We get an event that the WebGL context is lost
  • We get an event that its back available again, like onfocus or similar
  • We can reinitialize our shader programs / glw wrapper and resume rendering
  • Notify the app dev framework this has happened accordingly

Moved over from an original L2 issue:
rdkcentral/Lightning#469

More importantly this particular comment:
rdkcentral/Lightning#469 (comment)

cc @erikhaandrikman

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions