Safari 13 – Problem with Input field design

Home Forums Product Support Forums Ajax Search Pro for WordPress Support Safari 13 – Problem with Input field design

This topic contains 13 replies, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 10 months ago.

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #35733
    morethandigital75
    morethandigital75
    Participant

    Hello there,

    I’m working on a customers project (https://schoneberg.kunden-projekte.com/) and we faced a design problem in Safari 13 with the Search Input field. The design definitions seem not to apply and the input field appears in a non-styled manner.

    Attached you can find two screenshots. One screenshot of the input field in the latest version of firefox, where everything is fine. And one screenshot of the input field in Safari 13.

    Is there any way how we can fix this with CSS?

    Thanks,
    Christian

    #35738
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi Christian,

    Unfortunately the screenshots didn’t came through, but I might know what is going on regardless.

    There is one known issue with certain IOS and safari versions on displaying the input fields properly. It is sort of a difference on how Safari and other webkit type browsers render some elements.

    This custom CSS should resolve it though:

    div div.asp_w.ajaxsearchpro input[type="search"].orig {
        -webkit-appearance: none !important;
    }
    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #35742
    morethandigital75
    morethandigital75
    Participant

    Thank you very much Ernest. This solved the problem.

    Another question. When I’m using the elementor editor I can’t save my pages as long “Ajax Search Pro” is activated. Is there maybe a known solution for this problem?

    Thanks,
    Christian

    #35755
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi Christian,

    No, that should not happen at all.

    Can you please add temporary back-end and FTP access? I would like to debug the issue, to see if there is any 3rd party conflict or something similar.

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #35801
    morethandigital75
    morethandigital75
    Participant
    You cannot access this content.
    #35802
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #35806
    morethandigital75
    morethandigital75
    Participant
    You cannot access this content.
    #35807
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #35815
    morethandigital75
    morethandigital75
    Participant
    You cannot access this content.
    #35818
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #35834
    morethandigital75
    morethandigital75
    Participant
    You cannot access this content.
    #35835
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #35836
    morethandigital75
    morethandigital75
    Participant
    You cannot access this content.
    #35837
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic.