joris97jansen
@joris97jansen
Followers
479
Following
8K
Media
625
Statuses
4K
🛜🌐 - CEO @ The Borrowser https://t.co/TyvaPzipEc
The Borrowser HQ
Joined September 2022
Working on buttons in the Borrowser; mainly the correct rendering of them. But also trying to connect buttons + forms and therefor form submission. Not sure if it will fit in a single MR, but still really fun stuff to explore and work on!
0
0
2
Last bit of shareholder value for the Sunday evening: made sizing rules less “random” and more consistent. https://t.co/BxGki4Vs4r
github.com
Description Buttons appear everywhere; even without form submission, you want them to render and click-highlight. Key tasks Treat as an inline-level box (replaced-like) OR an inline ...
0
0
3
Yet another small refactor, which enables storing input values in the value store properly. https://t.co/u24GREX9lu
github.com
Resolves #137
0
0
2
Refactored a bit of the focus on input fields to receive keyboard events. It was a bit 'buggy' before, but this version should definitely be better! https://t.co/oFLKBLlACI
github.com
Resolves #136
0
0
6
In ~5 months, I was able to write over 6000 lines of code for the Borrowser, next to having a full-time job. Not sure if it is a lot, but I'm proud! https://t.co/MUKdXIGmhF
github.com
Built on-top of the Borrow Checker, not borrowed from Chromium. - joris97jansen/borrowser
2
0
4
Hrefs are working as well as browser history🚀 Small pieces starting to fall into it's place and this hobby project might turn into something real! https://t.co/YfXrOLlp6v
1
0
4
Good morning X! Feeling a bit better compared to yesterday, and decided to at least wrap up the basic implementation of the <input> element. Placeholder, clicking, writing text in it is working. A lot of room for improvement, but still another great achievement!
0
0
1
The concept of hrefs is working in the Borrowser. Not sure if it was this specific feature or the cold that I caught that made implementing this harder. But at least I got something done today🫡
0
0
3
Caught a cold last night, runny nose, sore throat, headache, you get it. Work has been very slow today, might not finish even a single issue today.😂
0
0
1
And with that, we've added some default href styling && fixed a nasty bug where we trimmed down text inside a node, which resulted in losing whitespace! https://t.co/hV4V2YqBNN
1
0
3
There is a nasty bug somewhere in the code, which results in whitespaces not showing up in the rendered HTML. I still have no clue what I got myself into 😭
3
0
6
So many AI replies here. Posting the most ridiculous screenshot of the ugliest UI you've ever seen. With a high-level technical explanation of how some Browser internal engine components work. And the reaction I get is: "Wow, this looks beautiful!", or even worse: "I've
1
0
3
Visualised how the cursor position is mapped to actual HTML elements for debugging & development reasons https://t.co/ymX5b6iGdC
1
0
5
Some more fundamental background work has been added, and elements needed stable IDs, so that we can store input values and later support clicking links. Darn, Browsers are VERY complex pieces of software! https://t.co/jZB4BGFKhV
github.com
Resolves #131
0
0
3
I’ll say it once more; the Borrowser is the next Browser you’ll love.
Mozilla has a new CEO and he just announced that Firefox will evolve into a modern AI browser. This is a good example of how management doesn’t understand its own user base and why they go out of their way to install Firefox on Windows, Android, iOS and other devices.
0
1
2
The whole F’ing reason why I’m building the Borrowser. LFG🚀
@theo Nah, they need to make money to keep that sinking ship alive. Chrome and every other browser are going to do this as well
0
0
2
Another piece of shareholder value just dropped: storing input values outside of the DOM. Nothing visual was added, just some HTML engine stuff. https://t.co/s80UE4YnwO
github.com
Resolves #130
1
0
2
Not an actual input field yet. Let alone the styling of it. But yet another big step forward🚀 https://t.co/mAznoGfdjn
1
0
1