Live data from Hacker News

This Week in Servo 43 (submitted via Servo itself)

blog.servo.org

11–20 of 25 posts

Re: This Week in Servo 43 (submitted via Servo itself)

#11

Earlier quoted context omitted.

I wonder if anyone has thought of including screencasting in bug reporting for bugs in guis?

For anyone wondering how to do this on linux, I use recordmydesktop and ffmpeg to make small webms (~2mb). Highly recommend it. `recordmydesktop --windowid $(xwininfo)` and click the window you want to record. `ffmpeg -i out.ogv -o final.webm` and you're done! recordmydesktop is available in most distros afaik.

I used kazam to make this (and ffmpeg/convert to make it into a gif). But yeah, recordmydesktop works too.

Though it has a small bug where, when recording a single window, the mouse position isn't shown correctly in the final video. (Instead of showing where the mouse was relative to the window, it takes the absolute position of the mouse and scales it down to the window size)

Re: This Week in Servo 43 (submitted via Servo itself)

#12

Earlier quoted context omitted.

Haha. Maybe related: https://github.com/servo/servo/issues/4378

I wonder if anyone has thought of including screencasting in bug reporting for bugs in guis?

https://lookback.io lets you do that on mobile. The neatest implementations have it show up if the user shakes the phone.

Re: This Week in Servo 43 (submitted via Servo itself)

#13
post #4
post #3

The killer feature in this week's newsletter is an image of using Servo itself to post this link to HN :-)

I can appreciate the honesty of that video.

This bug (input field doesn't scroll automatically, but spills its text into the surrounding elements) is a good demonstration of just how many, many small details you have take care of when implementing a browser engine.

A really monumental task. The servo devs have my respect!

Re: This Week in Servo 43 (submitted via Servo itself)

#15

Earlier quoted context omitted.

I wonder if anyone has thought of including screencasting in bug reporting for bugs in guis?

For anyone wondering how to do this on linux, I use recordmydesktop and ffmpeg to make small webms (~2mb). Highly recommend it. `recordmydesktop --windowid $(xwininfo)` and click the window you want to record. `ffmpeg -i out.ogv -o final.webm` and you're done! recordmydesktop is available in most distros afaik.

How come passing $(xwininfo) works? xwininfo outputs a lot more than just the window ID

Re: This Week in Servo 43 (submitted via Servo itself)

#16
post #9
post #7

Earlier quoted context omitted.

We used to use LICEcap at my old work for that.

Wonderful, you just make aware of the software that do exactly what I need today :-)

There's also https://github.com/thetarkus/WebMCam which records in a more modern format than gif.

Re: This Week in Servo 43 (submitted via Servo itself)

#17
post #4

Earlier quoted context omitted.

I can appreciate the honesty of that video.

This bug (input field doesn't scroll automatically, but spills its text into the surrounding elements) is a good demonstration of just how many, many small details you have take care of when implementing a browser engine. A really monumental task. The servo devs have my respect!

Maybe I'm missing something hugely obvious, but shouldn't the input field be rendered using a native control which would preemptively eliminate that bug and reduce the need for rewriting code that's been written countless times before?

Re: This Week in Servo 43 (submitted via Servo itself)

#18
post #9

Earlier quoted context omitted.

Wonderful, you just make aware of the software that do exactly what I need today :-)

There's also https://github.com/thetarkus/WebMCam which records in a more modern format than gif.

On Windows only.

Re: This Week in Servo 43 (submitted via Servo itself)

#19

Earlier quoted context omitted.

This bug (input field doesn't scroll automatically, but spills its text into the surrounding elements) is a good demonstration of just how many, many small details you have take care of when implementing a browser engine. A really monumental task. The servo devs have my respect!

Maybe I'm missing something hugely obvious, but shouldn't the input field be rendered using a native control which would preemptively eliminate that bug and reduce the need for rewriting code that's been written countless times before?

There's probably many reasons, but one is that native controls don't support everything in CSS.
Post reply on HN