capacitor-community / photoviewer

PhotoViewer table images with fullscreen and sharing capabilities
MIT License
49 stars 12 forks source link

ios invisible close button when opens images list in a slider mode #36

Closed ivanov84 closed 1 year ago

ivanov84 commented 1 year ago

Describe the bug when user opens images list in a slider mode - close button is not visible because it's white. But when press on image to zoom mode and then press again to get back - you can see close button for 1 second and can press on it.

To Reproduce Open on ios images array in slides mode. const capImages: Array<Image> = ['image1.jpg','image2.jpg','image3.jpg']; const viewerOptions: ViewerOptions = {share: true, title: false}; const capOptions: capShowOptions = {images: capImages, mode: 'slider', startFrom: targetIndex, options: viewerOptions}; try { await PhotoViewer.show(capOptions); } catch (e) { console.error(Unable open image in photoviewer, e); }

Expected behavior black background or black close button or grey box under close button.

Screenshots image image image

Desktop (please complete the following information):

jepiqueau commented 1 year ago

@ivanov84 Which release of the plugin are you using? Have you tried with @capacitor-community/photoviewer@2.0.10

ivanov84 commented 1 year ago

@jepiqueau I will try next release and reply here.

ivanov84 commented 1 year ago

@jepiqueau same problem with new version 2.0.9 on ios.

The close button is invisible again when the one image is opened:

2023-05-11_14-44-54

Also some images in the new version are not loading correctly, I think because of the new version of native ios links. I downgraded to version 2.0.1 and it worked but with a hidden close button like in the new version:

2023-05-11_15-02-54

ivanov84 commented 1 year ago

@jepiqueau IMHO it could be ideal to realise this concept:

background color when opens image but when 1 click then - title hides - click again - show, double tap - zoom

IMG_5077 IMG_5078 IMG_5079

jepiqueau commented 1 year ago

@ivanov84 this has been fixed in 2.1.0 & 3.0.0-beta.1 releases