Removing the brain from millets -- dehusking -- could squander away the benefits of eating them, say the authors who studied five small Indian millets: foxtail, little, kodo, barnyard, and proso  

The list of top 10 investment banks this year includes only one foreign entity.

Domestic banks win on consistency, efficiency; HSBC is only foreign bank on top-10 list

Michelle Barker appears as one of a heavenly host, coming forth with scroll in hand to pronounce an end to janky scrolljacking! Unto us a new specification is born, in the city of TimBL, and its name shall be called Scroll Snap.

---

Sponsor: Order any Standard paperback(s) and get a surprise gift card in the box for YOU. While supplies last, from your pals at A Book Apart!

---

One area where the web has traditionally lagged behind native platforms is the perceived “slickness” of the app experience. In part, this perception comes from the way the UI responds to user interactions – including the act of scrolling through content.

Faced with the limitations of the web platform, developers frequently reach for JavaScript libraries and frameworks to alter the experience of scrolling a web page – sometimes called “scroll-jacking” – not always a good thing if implemented without due consideration of the user experience. More libraries can also lead to page bloat, and drag down a site’s performance. But with the relatively new CSS Scroll Snap specification, we have the ability to control the scrolling behaviour of a web page (to a degree) using web standards – without resorting to heavy libraries. Let’s take a look at how.

Scroll Snap

A user can control the scroll position of a web page in a number of ways, such as using a mouse, touch gesture or arrow keys. In contrast to a linear scrolling experience, where the rate of scroll reflects the rate of the controller, the Scroll Snap specification enables a web page to snap to specific points as the user scrolls. For this, we need a fixed-height element to act as the scroll container, and the direct children of that element will determine the snap points. To demonstrate this, here is some example HTML, which consists of a <div> containing four <section> elements:

<div class="scroll-container">
  <section>
    <h2>Section 1</h2>
  </section>
  <section>
    <h2>Section 2</h2>
  </section>
  <section>
    <h2>Section 3</h2>
  </section>
  <section>
    <h2>Section 4</h2>
  </section>
</div>

Scroll snapping requires the presence of two main CSS properties: scroll-snap-type and scroll-snap-align. scroll-snap-type applies to the scroll container element, and takes two keyword values. It tells the browser:

• The direction to snap
• Whether snapping is mandatory

scroll-snap-align is applied to the child elements – in this case our <section>s.

We also need to set a fixed height on the scroll container, and set the relevant overflow property to scroll.

.scroll-container {
  height: 100vh;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}

section {
  height: 100vh;
  scroll-snap-align: center;
}

In the above example, I’m setting the direction in the scroll-snap-type property to y to specify vertical snapping. The second value specifies that snapping is mandatory. This means that when the user stops scrolling their scroll position will always snap to the nearest snap point. The alternative value is proximity, which determines that the user’s scroll position will be snapped only if they stop scrolling in the proximity of a snap point. (It’s down to the browser to determine what it considers to be the proximity threshold.)

If you have content of indeterminate length, which might feasibly be larger than the height of the scroll container (in this case 100vh), then using a value of mandatory can cause some content to be hidden above or below the visible area, so is not recommended. But if you know that your content will always fit within the viewport, then mandatory can produce a more consistent user experience.

See the Pen Simple scroll-snap example by Michelle Barker (@michellebarker) on CodePen.

In this example I’m setting both the scroll container and each of the sections to a height of 100vh, which affects the scroll experience of the entire web page. But scroll snapping can also be implemented on smaller components too. Setting scroll snapping on the x-axis (or inline axis) can produce something like a carousel effect.

In this demo, you can scroll horizontally scroll through the sections:

See the Pen Carousel-style scroll-snap example by Michelle Barker (@michellebarker) on CodePen.

The Intersection Observer API

By implementing the CSS above, our web page already has a more native-like feel to it. To improve upon this further we could add some scroll-based transitions and animations. We’ll need to employ a bit of Javascript for this, using the Intersection Observer API. This allows us to create an observer that watches for elements intersecting with the viewport, triggering a callback function when this occurs. It is more efficient than libraries that rely on continuously listening for scroll events.

We can create an observer that watches for each of our scroll sections coming in and out of view:

const sections = [...document.querySelectorAll('section')]

const options = {
  rootMargin: '0px',
  threshold: 0.25
}

const callback = (entries) => {
  entries.forEach((entry) => {
    if (entry.intersectionRatio >= 0.25) {
      target.classList.add("is-visible");
    } else {
      target.classList.remove("is-visible");
    }
  })
}

const observer = new IntersectionObserver(callback, options)

sections.forEach((section, index) => {
  observer.observe(section)
})

In this example, a callback function is triggered whenever one of our sections intersects the container by 25% (using the threshold option). The callback adds a class of is-visible to the section if it is at least 25% in view when the intersection occurs (which will take effect when the element is coming into view), and removes it otherwise (when the element is moving out of view). Then we can add some CSS to transition in the content for each of those sections:

section .content {
  opacity: 0:
}

section.is-visible .content {
  opacity: 1;
  transition: opacity 1000ms:
}

This demo shows it in action:

See the Pen Scrolling with Intersection Observer by Michelle Barker (@michellebarker) on CodePen.

You could, of course, implement some much more fancy transition and animation effects in CSS or JS!

As an aside, it’s worth pointing out that, in practice, we shouldn’t be setting opacity: 0 as the default without considering the experience if JavaScript fails to load. In this case, the user would see no content at all! There are different ways to handle this: We could add a .no-js class to the body (which we remove on load with JS), and set default styles on it, or we could set the initial style (before transition) with JS instead of CSS.

Position: sticky

There’s one more CSS property that I think has the potential to aid the scroll experience, and that’s the position property. Unlike position: fixed, which locks the position of an element relative to the nearest relative ancestor and doesn’t change, position: sticky is more like a temporary lock. An element with a position value of sticky will become fixed only until it reaches the threshold of its parent, at which point it resumes relative positioning.

By “sticking” some elements within scroll sections we can give the impression of them being tied to the action of scrolling between sections. It’s pretty cool that we can instruct an element to respond to it’s position within a container with CSS alone!

Browser support and fallbacks

The scroll-snap-type and scroll-snap-align properties are fairly well-supported. The former requires a prefix for Edge and IE, and older versions of Safari do not support axis values. In newer versions of Safari it works quite well. Intersection Observer similarly has a good level of support, with the exception of IE.

By wrapping our scroll-related code in a feature query we can provide a regular scrolling experience as a fallback for users of older browsers, where accessing the content is most important. Browsers that do not support scroll-snap-type with an axis value would simply scroll as normal.

@supports (scroll-snap-type: y mandatory) {
  .scroll-container {
    height: 100vh;
    overflow-y: scroll;
    scroll-snap-type: y mandatory;
  }

  section {
    height: 100vh;
    scroll-snap-align: center;
  }
}

The above code would exclude MS Edge and IE, as they don’t support axis values. If you wanted to support them you could do so using a vendor prefix, and using @supports (scroll-snap-type: mandatory) instead.

Putting it all together

This demo combines all three of the effects discussed in this article.

Summary

Spending time on scroll-based styling might seem silly or frivolous to some. But I believe it’s an important part of positioning the web as a viable alternative to native applications, keeping it open and accessible. While these new CSS features don’t offer all of the control we might expect with a fully featured JS library, they have a major advantage: simplicity and reliability. By utilising web standards where possible, we can have the best of both worlds: Slick and eye-catching sites that satisfy clients’ expectations, with the added benefit of better performance for users.

---

About the author

Michelle is a Lead Front End Developer at Bristol web agency Atomic Smash, author of front-end blog CSS { In Real Life }, and a Mozilla Tech Speaker. She has written articles for CSS Tricks, Smashing Magazine, and Web Designer Magazine, to name a few. She enjoys experimenting with new CSS features and helping others learn about them.

More articles by Michelle

BoB Chief Debadatta Chand says FY25 credit, deposit growth targets revised down to balance CD ratio

Earlier in 2024, Sundaram Home Finance bolstered its presence in non-South regions with branch openings in Mumbai and Kota, Rajasthan

Union Bank of India opens Nari Shakti branches in Bengaluru, Chennai, Visakhapatnam, and Jaipur

Montreal : National Film Board of Canada, 2019

New York : Springer, 2005

Basel ; Boston : Birkhauser, 2007

[Place of publication not identified] : American Mathematical Society, 2011.

New York : Springer, 2005

Boston ; Berlin : Birkhäuser, 2006

New York : Springer, 2005

New York : Springer, 2007

Cham, Switzerland : Springer, 2021.

Singapore : World Scientific Publishing Company, 2022.

Cham : Springer International Publishing : Imprint: Springer, 2018.

Cham, Switzerland : Springer, 2018

Cham : Springer, 2019.

The IMA Rajoytsava award will be given away to a doctor, who has worked for the cause of Kannada and protection of environment

Presiding over the programme, cairman A.V. Ramana unfurled the Kannada flag in the presence of senior officials and office-bearers of NMP Kannada Sangha.

Vice-Chancellor Naima Khatoon said the judgment paved way for the granting of minority status to the varsity. Students celebrated the day by distributing sweets at the varsity gate.

Starts his next venture Twiddles, a guilt-free indulgence healthy food brand targeted at the youth and athletes

Forget memorable, the passengers are so irritating that one would rather hop off the film and abort the trip

The Dastkar Mela brings together handlooms and handicrafts from across the country

According to a source, the meeting was not a knee-jerk reaction to India’s series whitewash (0-3) at home by New Zealand

A commonly used blood thinner can be repurposed as an inexpensive antivenom treatment, a study published in Science Translational Medicine has said

The Braj Mandal Yatra route spans over nearly 80 km and ends at Singar via the Jhir temple

I've put a link to the new Library Reorganization Blog to our list of links (look on the right hand side). It appears that it is open for comments, whether named or anonymous.

We need to start brainstorming for ideas and features that we want on the new science portal so we'll be prepared for when we locate a web designer.

Here are a list of some other science library websites. Not all are great but I'd like for us to discuss what elements we like and which features we don't like (just as important). Please feel free to post links to other libraries you think are worthy of critique. Also, if there are general guidelines and features that you'd like to include please post about those too.

My first impression looking at these sites is how busy they all are. Lots of links and it seems overwhelming at first glance. Its a decision that we'll have to make about how much information should be quickly accessible on the main page but yet still easily usable. Caltech's library page is the most easily navigated, IMO. I like the quick drop down boxes and the selection of links. I especially like the menu for authors - as the issue of open access and author rights becomes more important on campus, we'll need to take an active role in helping the faculty understand their rights and options for publishing.


Berkeley: Chemistry: http://www.lib.berkeley.edu/CHEM/
Engineering: http://www.lib.berkeley.edu/ENGI/
Physics/Ay: http://www.lib.berkeley.edu/PHYS/

Caltech: http://library.caltech.edu/

Chicago : http://www1.lib.uchicago.edu/e/crerar/index.php3

Irvine: http://www.lib.uci.edu/libraries/science.html

Michigan: http://www.lib.umich.edu/science/

MIT Science Library: http://libraries.mit.edu/science/

Oregon Science Library: http://libweb.uoregon.edu/scilib/

Santa Cruz: http://libweb.uoregon.edu/scilib/

Full Schedule
Proceedings

Best quote: Librarians are like Mr. Paperclip from MS Office - we pop up when you least expect it and try to offer to you help...

This conference focused on the science library's role in supporting e-science and integrating into research collaborations and science departments. There was a mixture of speakers: government, library and institute directors, and a few librarians. The presentations were a mixture of big picture descriptions and some concrete examples. I felt like there wasn't as much hard solutions that we could take back to the library and implement, but perhaps just educating the library community on how radically different e-science is changing the research landscape is the necessary first step.

I've included the highlights from my session notes below (let me know if you'd like the see my full notes in gory detail). Check out the proceedings link above for powerpoint and document files for most of the speakers.

As a side note, our poster about GatorScholar was well-received with many people already aware of the project from either Val's USAIN presentations, the SLA poster, or from hearing about Cornell's project. Medha Devare was one of the panel reactors and she mentioned our collaboration in her presentation. Most of the poster visitors seemed very interested in starting their own version and perhaps at some point we'll have a network of databases.

Thursday

E-Science: Trends, Transformations & Responses

Convener and Moderator: Wendy Lougee, University of Minnesota
Speaker: Chris Greer, Director, National Coordination Office

2. A Case Study in E-Science: Building Ecological Informatics Solutions for Multi-Decadal Research

William Michener, Research Professor (Biology) and Associate Director, Long-Term Ecological Research Network Office, University of New Mexico


3. Rick Luce, Vice Provost and Director of University Libraries, Emory University Libraries

"Making a Quantum Leap to eResearch Support: a new world of opportunities and challenges for research libraries"


Wendy Lougee

Pitfalls: not to fall back on traditional roles, currently we don't respond to multi-institutional collaborations, our boundaries stop with the institution

We need to understand scientists' workflows, need to identify strategies for embedding librarians into project teams. We need to think about core expertise of librarians, reimaging roles of librarians

What do we do to build this collaborative action? We need to think outside the box.

Data Curation: Issues and Challenges

Convener and Moderator: James Mullins, Dean of Libraries, Purdue University

• Liz Lyon, Director, UKOLN

Transition or Transform? Repositiioning the Library for the Petabyte Era

How can libraries work with science (in a very general sense)?

1. Transition or Transform? Need to become embedded and integrated into team science. Many different models of engagement

Geosciences pilot where the library worked with the Geological department to curate their datasets (Edinborough):
Found: Time needed is longer than anticipated, inventory doesn't have to be comprehensive, little documentation exists
Outcomes: positive, requirement for researcher and auditor training, need to develop a data policy

2. Lots of opportunities of action: leadership by senior managers, faculty coordination, advocacy & tranining, data documentation best practices

People and Skills: there are not enough specialised data librarians. In UK 5 data librarians. Need to bring diverse communities together - facilitate cooperation between organizations and individuals.

Open science: new range of areas where results are being put onto the web (GalaxyZoo eg.) Librarians need to be aware of implications.

3. Need multidisciplinary teams and people in library, huge skill shortage, need to find core data skills and integrate it into the LIS curriculum. Recruit different people to the LIS team, rebrand the LIS career. Go from librarianship to Informatics.

• Fran Berman, Director of the San Diego Supercomputer Center, UC San Diego, and Co-chair Blue Ribbon Task Force on Sustainable Digital Preservation and Access

"Research and Data"

Researchers are detectives, shows different major questions (SAF, Brown Dwarfs, bridge stress, Income dynamics over 40 years, Disease spread-Protein Data Bank) - key collections all over.

CI Support: all these issues are crucial. researchers want a easy to use set of tools to make the most of their data.

She finds different preservation profiles: timescale, datascale, well-tended to poor, level of policy restrictions, planned vs. ad hoc approach

Researchers focused on new projects, customization of solutions to problems, collaboration

Researchers need help: developing management, preservation and use environments, proper curation and annotation, navigating policy, regulation, IP, sustainability

Questions about preservation: what should we save and who should pay for it? Just saving everything isn't an option. 2007 was the crossover year - digital data exceeded the amount of available storage. What do we want to save? Who is we?
Society: official and historically valuable data, Fed agency or inst normally takes part.
Research community: PDB, NVO.
Me: medical record, financial data, digital photos - real commercial market for preservation solutions.

What do we have to save?
private sector: HIPAA, Sarbanes-Oxley,
OMB regulations for fed funded research data (3 years, not always easy to do).

Economics: many costs associated with preservation. Maintenance upkeep, software, utilities, space, networking, security, etc.

UCSD forged partnership with library. Trying to create a preservation grid with formal policies, nationwide grid with other institutions.

Panel Responders:

• Sayeed Choudhury, Associate Dean of University Libraries and Hodson Director of the Digital Research and Curation Center, Johns Hopkins University

Data Curation Issues and Challenges:

It makes sense to help scientists deal with public and higher levels of data, not the raw data.

Considerations: need to work within their systems, consider gateways for systems as part of infrastructure development (think about railroad gauge), focus on both human and tech components of infrastructure, human interoperability is more difficult than tech interoperability, trust is key!

Questions: What about the cloud or the crowd? Can Flickr help us with data curation? What are the fundamental differences between data and collections? Human readable vs. machine readable? How do we transfer principles into new practices? What are we trying to sustain? Data? Scholarship? Our organizations?


Supporting Virtual Orgs

• Thomas A. Finholt, Director, Collaboratory for Research on Electronic Work (CREW) and Research Professor & Associate Dean for Research and Innovation, School of Information, University of Michigan

Changing nature of geographically-distributed collaboration:

history: transition in terms of distributed work. Much of what came before (collaboratory, video conf) had a precedent but new emerging has no precedent (crowdsourcing, VO's), no traditional context leaves us a bit adrift.

Lesson 1: anticipate cultural differences.
Domain scientists: characteristics: power distance (bias toward seniority, hierarchical), individualist(solo PI, individual genius), masculine(adversial and competitive), uncertainty avoidance
CI developers: power distance (bias toward talent, egalitarian), collectivist(project model), masculine, embrace risk

Lesson 2: plan for first contact.

It can be tough to recognize successful innovations: first efforts are often awkward hybrids



Crowdsourcing: idea that we send out challenges and solutions come to us (ex. Innocentive website, Games with a Purpose). We don't know who is going to do the work, effort is contributed voluntarily -> incentives are important to motivate work

Delegation of organizational work: people can count on organizations to do some of the basic policy work. Much attention has focused on technology and processes to support social ties, alternative course is the use of technology to supplant social ties - > think of this as organizing without the work of organizing, questions of who to trust, who pays, permitted to use the resources are managed by middleware.

Group work is an inevitable fact of org life.

• Medha Devare, Life Sciences and Bioinformatics Librarian, Mann Library, Cornell University

Idea of Virtual Organization: boundary crossing, pooling of competencies, participants or activities geographically separated, fluid, flat structure, participant equality

Library contributions: technology choices, tools; tech support/guidance; subject expertise; understanding of research landscape; vision - user needs of the future?

Examples of library support: VIVO, DataStar (supports data-sharing among researchers)

DataStar: Data Staging Repository: supports data sharing, esp during research process, promotes publishing or archiving to discipline specific data centers and/or to Cornell's DR. Nascent stage

Reinventing the library? Librarians as middle-ware to facilitate process of connecting and creating coherence across disciplines - both VIVO and DataStar aid this.

Hope that both tools seamlessly interact with each other.


D. Scott Brandt, Associate Dean for Research, Purdue University Library

Tries to embed librarians in research teams. We have to redefine what we do, collect.

And joining the players in celebration were their families.

Biden shared a message of hope and democracy, while Harris highlighted the importance of knowledge and peace in her Diwali message from the campaign trail

People hope Trump will address jobs, economy issues; Trump has vowed to crackdown on illegal immigration

‘The challenge of being the leader of COP30 next year, in the heart of the Amazon forest, is huge,’ said Marina Silva, Brazil’s environment minister and top climate diplomat, at an event recently

The victory, its first at home, helped Calicut jump over Kannur Warriors and move to the top of the table with 13 points from seven matches.