You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've run into an inconsistency in IE 10 support and flexbox. Is it just a fact that I need to make sure children of flexbox are display block?
This pen works as expected in webkit browsers and IE11. In IE10 however the flex:1; style on the .flex-child-label class seems to be ignored. If i make the .flex-child-label class be display:block it works as expected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@media screen and (max-width:919px){.tablet-only{display:none}.tablet-desktop-only{display:none}.not-phone{display:none}}@media screen and (max-width:1174px){.desktop-only{display:none}}@media screen and (min-width:920px) and (max-width:1174px){.not-tablet{display:none}}@media screen and (min-width:920px){.phone-only{display:none}}@media screen and (min-width:1175px){.tablet-only{display:none}.phone-tablet-only{display:none}.not-desktop{display:none}}.pub-actionlist-panel .res-button,.pub-main .res-button{height:28px;color:#3f393c;overflow:hidden;transition:all cubic-bezier(.215,.61,.355,1) 250ms;background-color:rgba(255,255,255,0);background:linear-gradient(to right,rgba(244,205,84,.53),#f4cd54,rgba(243,204,83,.61))}.pub-actionlist-panel .res-button:hover,.pub-main .res-button:hover{background:linear-gradient(to right,rgba(242,198,60,.53),#f2c63c,rgba(241,197,59,.61))}.pub-actionlist-panel .res-button--muted,.pub-main .res-button--muted{background:0 0;color:#ae6c00;background-color:rgba(174,108,0,.15)}.pub-
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Well, we're finally to that point. It's finally time to start inching the pubs module toward the new frontier. But, in light of that exciting new opportunity, we have some immediate decisions to make. To integrate with Vue, we need webpack, and webpack also implies the pubs codebase being exposed to ECMA2015(ES6) features for the first time. So we need to decide if integrating new ES6 capabilities holds any value in simplifying and cleaning up the pubs codebase. Additionally, the general code-bundling system and philosophy we were operating under previously has done a lot to shape the way we were dealing with certain angular features, and we should take this opportunity to reevaluate many of those choices, so that they don't bog us down in the future.
That in mind, I've mostly organized our decisions into three distinct migration paths, which generally follow a linear progression from 'quick-n-dirty' to 'slow-but-thorough'. I've generally graded each migra