Comment 9 for bug 898496

(In reply to Raphael Groner from comment #2)
> (In reply to Kevin Fenzi from comment #1)
> > In the past gtk3/webkit2 support was lacking a number of things.
>
> Because there's no official 0.6.0 release currently, those issues should be
> reported to upstream.

Sure. But landing it in rawhide when it's lacking a bunch of things is more likely to cause people to just use some other browser.

>
> > We will of course move to it with the next version as that will be
> > gtk3/webkit2 only.
>
> Nice. But it will break with the gtk2 enforcement as a (nice to have?)
> requirement of the Xfce spin. Since Xfce is delayed further with official(!)
> Gtk3 support, I am not sure if we could still promote Midori/Gtk3 as a
> featured part of it.

I'm not sure where you see that requirement. We have a number of gtk3 items on the Xfce spin right now... this would simply be one more.

> > I'm not sure what all you are asking here... the above is the plan, just
> > need upstream to release 0.6.0 and rawhide will get it. ;) I don't really
> > want to drop a snapshot in...
>
> Well, it's requested for rawhide only, at the moment. Maybe it's even worth
> a RFE for Fedora 22? What do you think? It may depend who is releasing
> faster, upstream or Fedora … :)

I'm not going to land a snapshot in rawhide, at least without more data on how functional it is.
This seems like a fine use for a copr... would you be willing to make one? Or I could do so.