Jump to content
Search Community

TRIPLESENSE REPLY

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by TRIPLESENSE REPLY

  1. On 27/4/2018 at 6:00 PM, GreenSock said:

     

    Well, besides it allowing the context menu? Not much that I can think of. :)

     

    OK, I won't consider the following words :)

    On 24/4/2018 at 9:33 AM, TRIPLESENSE REPLY said:

    - allowcontextmenu : true isn't a recommended configuration (citing Jack from your post: The context menu would actually cause problems in several scenarios (like long-taps on mobile devices, etc.)

    Thanks!

  2. Thanks a lot!

    There is no hurry, my project (cappellini.it, and its siblings Poltrona Frau and Cassina) won't be online within two weeks, and npm will take care of updating the libraries :)

    Just a last question: what may the collateral effect be in using allowContextMenu:true?

  3. Hi!
    Sooo....

    Looks OK on either on Chrome, Firefox, IE11 and Edge! :)
    allowContextMenu:true is still a mandatory parameter, but this is a good compromise :)

    Sidenotes:

    1. on Windows you can drag with right mouse button and looks like that on MacOS you can't.
    2. also on Mac, when allowContextMenu===false, it still attempts to open the link

    Thanks again for your assistance!
    Are you going to release the amend?

    • Like 1
  4. Hi again!
    Looks like that allowNativeTouchScrolling:false solves the trouble!
    Sorry for the misunderstanding: I was somehow confused by documentation:

    Quote
    allowNativeTouchScrolling:  Boolean - by default, allows you to native touch-scroll in the opposite direction as Draggables that are limited to one axis . For example, a Draggable of type : " x " or " left " would permit native touch-scrolling in the vertical direction , and type : " y " or " top " would permit native horizontal touch-scrolling.

     

    Thanks again, have a nice day

    Massi

    • Like 1
  5. 11 hours ago, GreenSock said:

    @TRIPLESENSE REPLY dealing with the huge variety of (and conflicting) ways that browsers handle mouse/pointer/touch/scroll events is really complex

    Oh, yes, I know it's like hell :) That's why we worship your work ;)

     

    11 hours ago, GreenSock said:

    Anyway, I think I figured out what was causing your particular scenario to act that way, and I posted an updated Draggable with a fix - https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/Draggable-latest-beta.js (uncompressed). Does that work better for you? 

     

    Bad news on this topic:

    See the Pen LmRRvM by massic80 (@massic80) on CodePen

    I injected the new script in the same pen (with new URL) and it still attempts to open a new tab, either on Chrome, Firefox, IE11 and Edge on Win 10

     

     

  6. Thanks @GreenSock

    no problem for the "latest" trouble :)

    As of allowNativeTouchScrolling, I considered the option and probably also tested it (I don't remember and now I can't test easily since I'm from a mobile), but isn't it meant for scrolling on draggable's perpendicular direction?

  7. Hi @Sahil,
    I'm astonished, since I didn't expect latest versions from the CDN to be that old

    https://cdnjs.cloudflare.com/ajax/libs/gsap/latest/TweenMax.min.js
    there must be a problem in cdnjs configuration, @GreenSock

    However, your pen doesn't work as well: I created that one by adapting a pen from another forum post, but I'm using the latest version in my local environment.

    Thanks for the notification!
    I also updated my pen, also adding ThrowProps from the links you reported.

  8. Hi all,

    I'm attempting to create a vertical draggable with for a "fashionable" effect, an everything works as expected on Android, but not on iOS.

    On Android, the page doesn't scroll when I swipe up on the draggable, and scrolls only when I tap outside of it.

    On iOS, bot IPhone and iPad, looks like the page has a priority on the draggable (or the swipe event "bubbles" from the draggable), thus the draggable stays almost in the same position, and the page scrolls.

    In this pen, the gray draggable scrolls into the black box, and overflows it for a maximum of half of the draggable height.

    How can I get the same behavior on the platforms?

    Thanks in advance!

    (It's better to test the pen in full page mode:

    See the Pen qYbpOL by massic80 (@massic80) on CodePen

    See the Pen qYbpOL by massic80 (@massic80) on CodePen

  9. Hi, thanks for the suggestion.

    I saw that post and tested the same parameter, but it's not enough. On my side, right-clicking "Test Link" in your pen opens the context menu but doesn't prevent the link to "work" (the popup blocker prevents the new tab from opening, when not disabled).

    However, even if it worked

    - having a different behavior between iOS and Windows doesn't keep me relaxed :)

    - a right mouse click should open a context menu or do nothing, not do the same of left click

    - allowcontextmenu : true isn't a recommended configuration (citing Jack from your post: The context menu would actually cause problems in several scenarios (like long-taps on mobile devices, etc.)

    In my opinion, there is something to tune up.

  10. Hi Carl,

    thanks for the quick response!

    Actually, I didn't check on a Mac: I just did and it behaves the same of yours.

    Unfortunately, on different Windows 10 machines, with both Chrome and Firefox, the link redirected to a blank box.

    I just modified the link, adding a target="_blank" attribute, and now the right click opens a new tab with Google.

  11. HI all,

    I just noticed that setting dragClickables to true allows to drag the <a> tags, but when the user attempts to right-click them they work just like they were left-clicked, and he is redirected.

    I updated @crabcreative's Pen with the parameter.

    See the Pen Qryyjv by massic80 (@massic80) on CodePen


    Is there any built-in workaround for this?

     

  12. On 3/11/2016 at 10:59 PM, OSUblake said:

    With a little bit of math we can actually apply a wave to a curved surface  :shock:

    See the Pen ?editors=0010 by osublake (@osublake) on CodePen

    Great example!
    Math behind "interpolate" and "tangent" functions isn't very immediate, since it merges several points: could you please help me out? :)
    I'm using it and trying to invert the direction of the waves, but while in previous examples setting

    var norm = 1- i / segments

    rather than

    var norm =  i / segments

     

    does the trick, in this case it doesn't work. It's probably due to the tangent or interpolation :)
    Massi

×
×
  • Create New...