Urgent.News

What's breaking now, across thousands of outlets.

Tech

Empty is a result. Loading is a state.

The result element exists. It even contains text. Unfortunately, the text says Loading... instead. The check is green before the useful result has arrived. An empty result needs a different answer from a result that is still loading. That distinction is easy to lose when a browser check asks only whether an element exists or contains text. Four outcomes, three checks Following a discussion about…

The result element exists, and it includes text. However, the text displayed reads "Loading..." instead of the desired content. The check indicates that the result is green, even before the relevant information becomes available. Distinguishing between an empty result and a result that is still loading can be challenging when a browser check only verifies whether an element exists or contains text. This distinction becomes clearer when a browser readiness assessment is conducted.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Attacking APIs — Skills Assessment Writeup

Introduction Walking through my solve of the Attacking APIs Skills Assessment. This one chains weak authentication flows, insecure password reset mechanisms, and a classic SSRF/Local File Inclusion…

  • Exploited authentication weaknesses to obtain JWT
  • Exploited insecure password reset mechanism to change flag
  • Identified and exploited file inclusion vulnerability

More from Thursday 1 October →