Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter alexsavillephotography

    (@alexsavillephotography)

    Oops doesn’t look like i can send screen prints ;-(

    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    No problem, i can run the validator myself.

    The alt for the fs button in lightbox will be added in the next version.

    The problem on ontouchstart is that the touch events are not officially defined in HTML5. They work, however…

    i also experience same issue

    Thread Starter alexsavillephotography

    (@alexsavillephotography)

    Hi Jacob,

    Thanks for getting back to me.

    Presumaby for anyone who is only interested in the photo of the day part of the app, it’s not that useful to have touch events…? Or perhaps give developers the choice? Maybe a switch that gave developers the choice to have html compliance or not might be a cool idea?

    Thanks

    Alex

    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    There is a way to add the touch event handlers direct to the dom in stead of using the html onevent=”handler()” construction. This, however, is quite a lot of programming work, and i really doubt if this is usefull other than only to obey the formal rules while every browser accepts it.

    If you proove me ( not just referring to opinions only please ) that having ontouch events specified by html has a negative influence on seo behaviour, i might consider to change the 43 locations in the code where this applies.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Seo concerns’ is closed to new replies.