Last post Feb 05, 2020 11:08 AM by ulaskayalar
Feb 02, 2020 01:45 AM|ulaskayalar|LINK
I am having some problems like Css and Ajax in my ASP.NET Webforms project. For example, when I test the site in responsive mode in Mozilla or Google Chrome,
all features run smoothly if I click with the mouse. When in touch mode, the :hover feature doesn't work for mozilla. But :hover works on Chrome. The common problem with both browsers is that I cannot click on some linkbuttons in the Repeater with the touchscreen.
Oddly enough, every repeater and every linkbutton doesn't have this problem. I click on the buttons with the Repeater ItemCommand event. There is an indecision for touch, I don't get any error when touch features in mozilla don't work. I sometimes get meaningless
errors in Chrome. I do not fully understand what is the problem. I would be glad if you could help.
Feb 02, 2020 03:42 AM|KathyW|LINK
Touch doesn't have :hover behavior. (How does your screen know where you are until you touch it?) A phone OS or a browser may try to get around this by triggering :hover briefly (if there is one) before a click event if fired, when touched.
It assumes you had to hover to reach the clicked element. But that's not a universal behavior.
As for not being able to click on linkbuttons, that makes no sense unless something is z-indexed above them, but transparent. Use browser tools and see if that's the case. Regardless, no one can do anything but guess, from only a description.
Feb 02, 2020 08:01 PM|ulaskayalar|LINK
The problem of not clicking the buttons was only for Chrome. The reason is that the button is located inside a div which is shown as ".class: hover i". The problem disappeared when we removed this css code. But this time: I can't show the div because I can't
take advantage of the hover feature. Instead, I tried using Panel and showing it in C #. This time the page started to refresh when I clicked the linkbutton in the repeater. I want to click asynchronously.
Feb 02, 2020 08:19 PM|KathyW|LINK
You are asking us to guess. How would a hover style change if a click was asynchronous or not? Post your code if you want help.
Feb 02, 2020 09:02 PM|ulaskayalar|LINK
You did not fully understand my problem, but you are criticizing it. I'm talking about having linkbutton asynchronous problem. I'm not asking to solve the :hover problem right now.
Feb 03, 2020 09:17 AM|Yongqing Yu|LINK
According to your description, we cannot know exactly what your problem is.
I suggest you provide your current code so that we will try to reproduce the problem with your code, which will help us solve the issue faster.
Feb 03, 2020 04:56 PM|KathyW|LINK
I did not criticize you. I pointed out that your descriptions assume we can guess your code and markup, which would be required to understand your problem. Post code if you want help.
Feb 05, 2020 11:08 AM|ulaskayalar|LINK
I'm sorry, I was a little nervous. I now understand that the problem is caused by a different CSS code.
'display: contents' code prevented the buttons from clicking in
Chrome. When you remove this code, 'Aw, Snap!' error was also removed.
This is just the solution of the click error. It's not about :hover. Thanks for your help.