onfocus="this.blur()" 추가

<a href="#" onfocus="this.blur()">



'Development > HTML' 카테고리의 다른 글

html - HTML DOM Events  (0) 2015.06.26
html - role attribute  (0) 2014.05.06
html - <meta> http-equiv Attribute, X-UA-Compatible  (0) 2014.04.29
html - content type  (0) 2014.04.15
HTML DOM  (0) 2014.03.06
Posted by linuxism
,


Using .stop() or .clearQueue() to avoid animation queues in jQuery

This is a common problem when animating with jQuery: let’s say you code a navigation with a soft animation on mouse hover, or an extra element appears when you hover a trigger element. If we hover several times in a row, every new animation won’t start until the previous one ends, creating a “queue” that will make the animation repeat several times (which usually is an unwanted effect).

This effect can be avoided using the .stop() method in our script:

$(".trigger-element").hover( function () { $(this).stop().animate({width:"100px"},500); }, function () { $(this).stop().animate({width:"80px"},500); } );

When .stop() is called on the element, the currently-running animation will be stopped, so the next one will start immediately instead of queueing. Unfortunately the .stop() method only works with animations, so if we want to avoid any other kind of function queue we should use .clearQueue() instead.

You can see a demo with both cases and you can get more information about .stop() and more information about .clearQueue().



source - http://blog.javierusobiaga.com/using-stop-to-avoid-animation-queues-in-jquer

reference - http://programmingsummaries.tistory.com/316








Posted by linuxism
,

fedora - fedora.next

System/Linux 2015. 6. 12. 09:01


Fedora.next

Fedora.next is an umbrella phrase for the planning for the next decade of the Fedora Project.

Contents

 [hide

Background

This all came out of a number of proposals at Flock 2013, including Architecture for a More Agile Fedora and Stephen Gallagher's suggestion that we use that architecture to design, build, and market three distinct Fedora products. This grew into a proposal accepted by the Fedora advisory board, and the formation of Initial Working Groups by FESCo.

Fedora Magazine Articles

For an in-depth look (but with slides so you can skim easily too, if you like), check out this (in-progress) series of articles in Fedora Magazine

Fedora Present and Future: a Fedora.next 2014 Update

Other Articles

Videos

Current State

We have five working groups. These are independent sub-committees of FESCo, with individual governance structures. Three of the groups are developing future Fedora target products — Fedora Workstation, Fedora Cloud, and Fedora Server. These groups have created basic descriptions of their plans for those products, and are now working on concrete plans for what changes those might require for Fedora 21 and beyond. The other two groups, Base Design and Environments & Stacks, are not producing specific products, but will help design the shared core on which everything is built, as well as "building blocks" on top of that.

Product Working Group activity reports (FESCo #1221)

Each of the product working groups submitted their PRDs as described in the board proposal, and these were approved by both FESCo and the Fedora Board.

Working groups


Other Fedora SIGs and Projects

Fedora.next Brand Design

What makes a "product"?

Of course, we're not selling anything, or offering commercial support. We use the term product to indicate a release artifact that we intentionally construct in order to address an identified segment of user needs. In June 2014, the Fedora Project Board defined these general guidelines for possible future products:

  • Addresses a new, relevant, and broad usecase or userbase that a Fedora Product is not currently serving"
  • The usecase should be something the Board sees as being a long term investment
  • The Product should be coherent with all of Fedora's foundations


Original Announcements

  • Product Working Groups


source - http://fedoraproject.org/wiki/Fedora.next


Posted by linuxism
,