Skip to content
This repository has been archived by the owner on Jul 27, 2018. It is now read-only.

Servo + Browser.html: webplatform bugs #562

Closed
62 of 92 tasks
paulrouget opened this issue Aug 7, 2015 · 24 comments
Closed
62 of 92 tasks

Servo + Browser.html: webplatform bugs #562

paulrouget opened this issue Aug 7, 2015 · 24 comments
Assignees

Comments

@paulrouget
Copy link
Contributor

I'm retiring this meta bug. Maintaining this list is difficult for many reasons. I will use A-browserhtml tags in servo/servo and glennw/webrender for now.

A list summarizing all the browser.html + servo bugs can be found here: http://paulrouget.com/bhtml-servo-issues/


P1

Webrender P1

P2

P3

Webrender P3:

osx titlebar:

We can work around these issues:

Nice to have:

Long run issues:

Dynamic toolbar support:


Fixed

@frewsxcv
Copy link
Contributor

frewsxcv commented Aug 7, 2015

Possibly relevant issue: servo/servo#5394

@paulrouget
Copy link
Contributor Author

I'd like to focus on a minimal servo-based runtime. What we did for Gecko (graphene project).

I see 3 major area of work for now:

  • implementing enough of the web standards to be able to render browser.html. For example, calc(), devicePixelRatio, and fix some layout and painting bugs. This include making sure React works properly. I will be filing bugs in servo/servo and reference them here.
  • implement enough of the Browser API to support browser.html. There's already an experimental API. Maybe the best way to start is to write tests.
  • packaging and OS integration. For example, on osx, we want to create a .app package, register the app as a browser at the os level, delegate titlebar drawing to the html app (with the close/minimize/maximize buttons), and so on. I'm thinking of starting with OSX as it's the platform I know best (and already did all of that for gecko). I need to come up with a list of features we need to implement and figure out where they should be implemented (glutin vs. servo's port).

There's a lot more work required. Implementing some missing APIs (indexeddb, settings api, pointer events or gestures...), implement multiprocess, session restore, scroll grab, scroll snapping, performance, security model… but I guess we can live without these for now (and some of these tasks are already being worked on).

@paulrouget
Copy link
Contributor Author

I've already started filing bug and I'm working on porting servo to the latest version of glutin (more OS-level features like with_decoration(false)).

@pcwalton
Copy link

Exciting! I'm up for taking down the layout bugs as you come to them (and I've already started on some of the ones you've filed), since they tend to affect Web content too.

@pcwalton
Copy link

@paulrouget Could you elaborate on why multiprocess is important to browser.html?

@pcwalton pcwalton reopened this Aug 11, 2015
@paulrouget
Copy link
Contributor Author

@paulrouget Could you elaborate on why multiprocess is important to browser.html?

It is not important. It's not blocking browser.html development. But I assume it will be necessary if we ever ship a product based on servo + browser.html.

@waddlesplash
Copy link

servo/servo#7067 has been fixed, so that can be checked off.

@paulrouget
Copy link
Contributor Author

@pcwalton, if you have the opportunity to look at some more layout bugs: servo/servo#7166 servo/servo#7281 are the most annoying ones.

@paulrouget paulrouget changed the title Servo port tracking bug Servo + Browser.html: webplatform bugs Aug 26, 2015
@gordonbrander gordonbrander added this to the Motion sprint milestone Sep 9, 2015
@waddlesplash
Copy link

servo/servo#7571 has been fixed.

@waddlesplash
Copy link

Oh, also servo/servo#7218 & servo/servo#7064.

@notriddle
Copy link
Contributor

servo/servo#7828 is closed.

@notriddle
Copy link
Contributor

servo/servo#7780 was fixed by servo/servo@d572f1c.

@notriddle
Copy link
Contributor

servo/servo#8325 is closed.

@gordonbrander
Copy link
Contributor

Draggable regions: servo/servo#7408 ought to be P1, no?

@paulrouget
Copy link
Contributor Author

Draggable regions: servo/servo#7408 ought to be P1, no?

There's already a draggable zone, it's just not configurable in CSS.

@gordonbrander
Copy link
Contributor

There's already a draggable zone, it's just not configurable in CSS.

NVM :)

@waddlesplash
Copy link

servo/servo#8329 is fixed.

@mbrubeck
Copy link

servo/servo#8080 is fixed

@gordonbrander
Copy link
Contributor

@paulrouget vh and vw units are not recalculated after window resize servo/servo#8754. P2? We might be able to work around it, but it will be difficult.

This also causes problems with the positioning of child elements servo/servo#8754 (comment). For example, we use position:absolute centering approach for browser.html in several places as an alternative to flexbox (which Servo currently lacks).

Update: we're working around this by using percent instead of vw and vh #752.

@gordonbrander gordonbrander modified the milestones: Motion sprint, Mozlando Nov 30, 2015
@glennw
Copy link

glennw commented Jan 8, 2016

@glennw
Copy link

glennw commented Jan 14, 2016

@paulrouget https://github.com/glennw/webrender/issues/134 is fixed - however the bug fix was specific to perspective(0) - there is probably still bugs with real (nested) perspective values. I'll be working on those today and tomorrow.

@glennw
Copy link

glennw commented Jan 14, 2016

@glennw
Copy link

glennw commented Jan 15, 2016

@paulrouget
Copy link
Contributor Author

I'm retiring this meta bug. Maintaining this list is difficult for many reasons. I will use A-browserhtml tags in servo/servo and glennw/webrender for now.

A list summarizing all the browser.html + servo bugs can be found here: http://paulrouget.com/bhtml-servo-issues/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants