Magento-2 jquery widget timing issue The 2019 Stack Overflow Developer Survey Results Are In

Why don't Unix/Linux systems traverse through directories until they find the required version of a linked library?

I looked up a future colleague on LinkedIn before I started a job. I told my colleague about it and he seemed surprised. Should I apologize?

What is the use of option -o in the useradd command?

What is the motivation for a law requiring 2 parties to consent for recording a conversation

How are circuits which use complex ICs normally simulated?

Time travel alters history but people keep saying nothing's changed

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

What is the meaning of Triage in Cybersec world?

Is bread bad for ducks?

A poker game description that does not feel gimmicky

JSON.serialize: is it possible to suppress null values of a map?

Lethal sonic weapons

Does a dangling wire really electrocute me if I'm standing in water?

Spanish for "widget"

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

How to make payment on the internet without leaving a money trail?

How long do I have to send payment?

What does Linus Torvalds mean when he says that Git "never ever" tracks a file?

Does it makes sense to buy a new cycle to learn riding?

How to deal with fear of taking dependencies

Why is it "Tumoren" and not "Tumore"?

Deadlock Graph and Interpretation, solution to avoid

Could JWST stay at L2 "forever"?

Inline version of a function returns different value than non-inline version



Magento-2 jquery widget timing issue



The 2019 Stack Overflow Developer Survey Results Are In



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I recently started using jquery widgets in magento and come to know that magento extends jquery-ui widgets through the use of widget factory and customises them according to need and then again return them.



So far according to theory all looks good but as soon as I started using them, I found little timing issue in collapsible widget.



I am trying to use collapsible widget of magento inside one of my cms-block through data-mage-init. Here is how my structure looks.



<div class="top-header-link" data-mage-init='"collapsible":"animate": "duration": 500, "easing": "easeOutCubic" '>
<div class="trigger-top" data-role="title">Trigger element</div>
<div class="top-menu" data-role="content">
This is the element that should be collapsed and expanded.
</div>
</div>


Now when I cleared the cache and then reload the frontend, I noticed the element with attribute data-role="content" remains open by default and hides after whole page completes loading.



Now my question is how to solve this timing issue despite using magento jquery widget with proper way?



Should we use our custom jquery despite having collapsible widget?



Thanks in advance.









share




























    0















    I recently started using jquery widgets in magento and come to know that magento extends jquery-ui widgets through the use of widget factory and customises them according to need and then again return them.



    So far according to theory all looks good but as soon as I started using them, I found little timing issue in collapsible widget.



    I am trying to use collapsible widget of magento inside one of my cms-block through data-mage-init. Here is how my structure looks.



    <div class="top-header-link" data-mage-init='"collapsible":"animate": "duration": 500, "easing": "easeOutCubic" '>
    <div class="trigger-top" data-role="title">Trigger element</div>
    <div class="top-menu" data-role="content">
    This is the element that should be collapsed and expanded.
    </div>
    </div>


    Now when I cleared the cache and then reload the frontend, I noticed the element with attribute data-role="content" remains open by default and hides after whole page completes loading.



    Now my question is how to solve this timing issue despite using magento jquery widget with proper way?



    Should we use our custom jquery despite having collapsible widget?



    Thanks in advance.









    share
























      0












      0








      0








      I recently started using jquery widgets in magento and come to know that magento extends jquery-ui widgets through the use of widget factory and customises them according to need and then again return them.



      So far according to theory all looks good but as soon as I started using them, I found little timing issue in collapsible widget.



      I am trying to use collapsible widget of magento inside one of my cms-block through data-mage-init. Here is how my structure looks.



      <div class="top-header-link" data-mage-init='"collapsible":"animate": "duration": 500, "easing": "easeOutCubic" '>
      <div class="trigger-top" data-role="title">Trigger element</div>
      <div class="top-menu" data-role="content">
      This is the element that should be collapsed and expanded.
      </div>
      </div>


      Now when I cleared the cache and then reload the frontend, I noticed the element with attribute data-role="content" remains open by default and hides after whole page completes loading.



      Now my question is how to solve this timing issue despite using magento jquery widget with proper way?



      Should we use our custom jquery despite having collapsible widget?



      Thanks in advance.









      share














      I recently started using jquery widgets in magento and come to know that magento extends jquery-ui widgets through the use of widget factory and customises them according to need and then again return them.



      So far according to theory all looks good but as soon as I started using them, I found little timing issue in collapsible widget.



      I am trying to use collapsible widget of magento inside one of my cms-block through data-mage-init. Here is how my structure looks.



      <div class="top-header-link" data-mage-init='"collapsible":"animate": "duration": 500, "easing": "easeOutCubic" '>
      <div class="trigger-top" data-role="title">Trigger element</div>
      <div class="top-menu" data-role="content">
      This is the element that should be collapsed and expanded.
      </div>
      </div>


      Now when I cleared the cache and then reload the frontend, I noticed the element with attribute data-role="content" remains open by default and hides after whole page completes loading.



      Now my question is how to solve this timing issue despite using magento jquery widget with proper way?



      Should we use our custom jquery despite having collapsible widget?



      Thanks in advance.







      magento2 frontend jquery





      share












      share










      share



      share










      asked 1 min ago









      Shashank BhattShashank Bhatt

      3318




      3318




















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "479"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f269448%2fmagento-2-jquery-widget-timing-issue%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Magento Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f269448%2fmagento-2-jquery-widget-timing-issue%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

          How to solve knockout JS error in Magento 2 Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?(Magento2) knockout.js:3012 Uncaught ReferenceError: Unable to process bindingUnable to process binding Knockout.js magento 2Cannot read property `scopeLabel` of undefined on Product Detail PageCan't get Customer Data on frontend in Magento 2Magento2 Order Summary - unable to process bindingKO templates are not loading in Magento 2.1 applicationgetting knockout js error magento 2Product grid not load -— Unable to process binding Knockout.js magento 2Product form not loaded in magento2Uncaught ReferenceError: Unable to process binding “if: function()return (isShowLegend()) ” magento 2

          Nissan Patrol Зміст Перше покоління — 4W60 (1951-1960) | Друге покоління — 60 series (1960-1980) | Третє покоління (1980–2002) | Четверте покоління — Y60 (1987–1998) | П'яте покоління — Y61 (1997–2013) | Шосте покоління — Y62 (2010- ) | Посилання | Зноски | Навігаційне менюОфіційний український сайтТест-драйв Nissan Patrol 2010 7-го поколінняNissan PatrolКак мы тестировали Nissan Patrol 2016рвиправивши або дописавши її