TRACKING · Tracking record

coolwulf’s browser work · Records and changes

coolwulf’s browser-development history and new-project practice, keeping previous projects and new plans distinct.

00
UNDERSTANDING · What we know

Uses, conditions and important changes.

Each record has its own date and scope; these do not establish the live state of the whole product.

coolwulf’s browser work · Recorded by the site · 24 Aug 2026 · Earlier coverage

Twenty years on, the K-MeleonCCF author returns to V2EX to build a browser against Chrome

The author self-reports having built the Gecko-based K-MeleonCCF browser twenty years ago — before Firefox shipped — to break the IE monopoly, and now announces building a browser from scratch to take on Chrome's. The thread reached 103 replies, mostly debating engine monopoly and whether an independent browser can survive.

The track record comes from the founder-self-report and a discussion snapshot; no code or usable release exists yet, and reply volume is attention, not proof of the product.

Read the record and sources →

01
THE FULL RECORD · Full timeline

3 events retained by the site.

This object’s records stay together across live coverage, the watch pool and history. Every event links to its source record; corroboration and material changes have separate labels.

Dates use Beijing time. Open an event for its full record, original source and evidence. Corroboration adds support without counting as a material change.

02
COVERAGE · Record status

No live card right now.

Coverage status describes how this site maintains its records, not whether a product is worth using. Existing records remain available after leaving the current list.

Registered follow-up scope

These are registered scopes, not complete product coverage or a receipt for the latest successful check.

03
THE LINEAGE · Lineage

An ongoing record around the same identity.

Source evidence identifies this line. Changing category or moving into history does not create a new identity.