It’s working now, thanks Yigit!

Excellent as usual, Rikard! thanks so much. You can definitely close the ticket!
For everyone in the future wondering what he added to my CSS, here it is. I am not sure it is ok for everyone, but at least it is something you can experiment.
Bye!
A.-

@media only screen and (max-width: 1300px) {
  nav.main_menu {
    display: block !important;
  }
  #avia-menu .menu-item {
    display: none;
  }
  .av-burger-menu-main.menu-item-avia-special {
    display: block;
  }
}

@media only screen and (min-width: 768px) and (max-width: 990px) {
  span.logo img {
        padding-top: 25px;
}
}

IT IS WORKING!!!!

Thank you, thank you very much for having spent so much time trying to fix this one!

Isn’t the Horizontal Gallery working definitely better this way on mobile phones?? I still cannot understand how the “standard” behaviour is acceptable by other people! :) If I tap on an image on the horizontal gallery, it must open directly in the lightbox, period!

Well, who cares why other people like to have an intermediate tap? Today I am happy! :-)
Thanks, thanks so much.
Bye!
A.-

Thanks Ismael!

But on IOS (I cannot check on Android) it is still showing me the “<= =>” enlarge icon after the first tap, and then opening it in the lightbox only after the second tap.
You can check for example with this one:you’ll find an horizontal gallery just below the first descrption section.

Thnks for yout efforts, Ismael!
But what I don’t understand is: this behaviour should be annoying for everyone, isn’t it? If I see a picture on the screen, I want to enlarge it by tapping on it once. Why should I tap on it TWICE, just to make a useless “enlarge icon” appear on firts tap? :)
THX
Bye!
A.-

Hi @Rikard. I already explained in my first message that I already did what you are asking to test.
1) I removed the whole CSS
2) I set the Default Content Font Size to a large value
3) Cleared the cache, opened the website: the default text is still unchanged.

But I did it once again. In these screenshots you can see:
1) Set the default font size to 70px (all the 4 values, just to be sure it is not mistakenly skipping the first value): https://imgur.com/a/lZNGH0E
2) cleared the whole CSS area (you can see that it is also “saved” already: https://imgur.com/a/qJzNRMb
3) See the normal text when I access no matter what page (you can see that I am also in incognito mode): https://imgur.com/a/iSjGTmo

Therefore, as I said in my previous messages, the Default Content Font Size seems NOT to be working.
I also wrote already that the H1, H2, H3… values in Typography are working fine. The only one that seems not working is the Default Content Size.

Bye,
A.-

Sorry @Rikard, I did not understand that you were referring to the page example link :-) Fixed it, thank for your patience…

Yep, it’s 5.1.1. In fact I’ve just deactivated the “full width mode”, and the bar stopped floating. Thanks Rikard! Issue closed.

As I said, it is useful to have the elements always available: you can drag the elmenet from the bar and drop it exactly where you want, instead of dragging it down the whole page (and if you have long pages, it’s quite annoying). But it is giving other side effects, like (as I mentioned) the fact that you cannot drag an element along the page anymore, because the page does not scroll automatically when you drag the item at the limit of the page. Then, sometimes the floating bar is hiding some parts of the page…. therefore: it’s a rather “good bug” :-)

Bye!
A.-

• This reply was modified 3 years ago by mistermagoo8691.

Hi @Yigiyt.
Wow, I see, in fact I was also using // for comments… but CSS seemed to me to be working quite well! OK, I will stop using it.

Second: no, I don’t see a simple border. I see a colored button!, that remains the same both in “transparent” and “opaque” mode!
I made sure to clean the cache, I connected in incognito mode, I connected from a PC where I never launched the website…. no changes, I always see the colored button.

See below what I see (in the top part of the image): I’ve also added (in the bottom part) what I’d like to achieve :-)

https://imgur.com/a/ysEMT0y

Thanks for your help!
Bye,
A.-

Hi @Yigit, thanks for your help!

What are the errors in my comments that you fixed?
Because I know that comments must be written between /* and */. Normally I am commenting out parts of the CSS “extending” the closure of the comment, therefore this is why you may have found some parts of the CSS that start with a /* before the comment, and then they have the */ only at the end of the style… it is on purpose, this way I have deactivated that part of the CSS.
Is this the type of error you are referring to?

Said that: ok, now I can edit the “Menu Item Button With Border” style.
But:
1) in the “Menu Item Button With Border” I can only change font color and border color. I cannot change the background of the button (now it is using a green that is the same of my buttons), the background of the item (now it is BLACK, and it is different than the dark gray of my meny bar)….
2) how can I make it transparent when the homepage is first loaded (and the header is transparent)?

My goal is quite simple from a styling standpoint: i just want to have a white border around one menu item (white color, like the existing menu text itself).
No color to fill the button: the background must change according to the background of the menu bar (which is transparent as soon as you open the page, and then changes to dark gray)

Thanks again and bye!
A.-

Hi @Ismael. I’ve added the script, but almost nothing changed.

Please note: I’ve added it to the existing snippet, therefore now I have both:

/* old snippet */
#top .av-horizontal-gallery-link {
    width: 100% !important;
    height: 100% !important;
    background: transparent !important;
    transform: none !important;
}

/* new snippet */
#top .av-horizontal-gallery-link:before {
position: absolute;
    right: 10px;
    bottom: 0;
}

There is only one small change: the icon now appears in a different position, as you said.

But please note: my goal is different: I want to open the image in the lightbox as soon as I tap on it, immediately. The “expand” icon is useless.

Now it works like this: 1) I tap on an image in the horizontal gallery on my mobile => 2) the useless “expand” icon appears (useless, because the image size does not change at all) => 3) I need to tap again in order to open it in the lightbox. I want to go from (1) to (3) directly.
Please note: it work exacytly like this on PC!

@Mike wrote that it happens on IOS only, and he was looking for a device to test it…

THX
Ciao,
A.-

• This reply was modified 3 years ago by mistermagoo8691.

Hi Mike. See the attached video. I am using Chrome on an iPhone.

https://www.youtube.com/shorts/U4-e40FQ_nY

As you can see, the firts tap on the image shows the “enlarge” icon (it is not visible in full, you can see half of that), and then only the second tap opens it in the lightbox.

As I explained above, I’ve added the CSS below after the suggestion on @nikko in the mentioned thread, because I wanted to open the lightbox on the first click on PC (and I thought it worked on mobiles on first tap too).
Well, it works fine on the PC… but it does not work on mobile (apparently on IOS only, based on what you told me)!

#top .av-horizontal-gallery-link {
    width: 100% !important;
    height: 100% !important;
    background: transparent !important;
    transform: none !important;
}

THX
Ciao!
A.-

Wow, that’s a hard one, isn’t it? I just wanted to know if you cannot support me because you don’t understand the problem… in this case I can add several screeshots (or even a video, if this can help….)
Thanks!

Found it! Thanks Rikard. You may update that document page, so that future users will not get confused like me…
Thanks again & bye,
A.-

Thanks Rikard, you can close it. The fix fixed it :)
Bye,
A.-

Oh, I see, I did not know that.
Ok, done: nothing changed, same result. The preview button is not “previewing” the latest version, also using the Classic Editor.

It is absolutely weird, but I will eat and digest it if there are currently no solutions.

I think it is something that needs to be fixed, though, because it is very annoying for an unexperienced user: the first time it happened, I thought that my page was broken, and I rebuilt the whole page from scratch (my pages are very complex)…

When it happened the second time on another page, I was going to rebuild it again, then I realized by chance that the page was actually correctly working, and the issue was in the “Preview” function only.

Thanks RIkard for your help, as usual.
Bye!
A.-