search

Cosmic-Chatter / Exhibitera

Free and open-source software for building and controlling museum exhibits.
MIT License
2 stars 2 forks source link

Image as background obscures content in Media Browser #29

Closed David-S-Morgan closed 2 days ago

David-S-Morgan commented 5 days ago

I think this is a bug -- selecting an image to use as a background in Media Browser results in the content items being completely hidden behind the image.

forceflow1049 commented 5 days ago

@David-S-Morgan I can't reproduce this—see the attached screenshot. Can you provide any details to reproduce?

Screenshot 2024-09-12 at 4 21 09 PM
David-S-Morgan commented 4 days ago

It appears to be an issue with Firefox (at least on Linux). Works fine in Chromium, but even starting Firefox in safe mode (which disables extensions and customizations) I see the background only.

David-S-Morgan commented 4 days ago

Here's a screenshot -- left side is Chromium, right side is Firefox. (Ignore how ugly this looks -- it's very much a work in progress!)

Screenshot from 2024-09-13 09-32-54

forceflow1049 commented 4 days ago

Aren't browsers grand? This is good feedback and I'll see if I can track it down.

David-S-Morgan commented 4 days ago

Heh, yes indeed. FWIW we use Chromium for our production exhibits, so this isn't a show stopper for us.

On Fri, Sep 13, 2024 at 11:07 AM Morgan Rehnberg @.***> wrote:

Aren't browsers grand? This is good feedback and I'll see if I can track it down.

— Reply to this email directly, view it on GitHub https://github.com/Cosmic-Chatter/Exhibitera/issues/29#issuecomment-2349178074, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2QASTPJBUKEGFWB2E4DODZWL5SNAVCNFSM6AAAAABOD4EP2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBZGE3TQMBXGQ . You are receiving this because you were mentioned.Message ID: @.***>

forceflow1049 commented 2 days ago

@David-S-Morgan this is fixed in https://github.com/Cosmic-Chatter/Exhibitera/commit/ea103b604478d1a6e95c1c825a5a895b0e15b4f3 which will be included in 5.2.

This was a really weird bug... it actually seems like it shouldn't have been working in Chromium or Webkit at all. But it even worked in Firefox until recently, because I hd to update Firefox to even be able to reproduce this.