**** BEGIN LOGGING AT Tue Oct 07 03:00:00 2014
Oct 07 04:50:42 <irc_smirk> hello
Oct 07 16:49:16 <dmanderson> morning irc_smirk
Oct 07 17:01:03 <GodGinrai> ?_?
Oct 07 17:01:13 <GodGinrai> no morning for the rest of us, dmanderson? :P
Oct 07 17:01:18 <dmanderson> LOL
Oct 07 17:01:20 <dmanderson> morning all
Oct 07 17:01:21 <dmanderson> :-p
Oct 07 17:01:52 <GodGinrai> that's more like it ;)
Oct 07 17:47:06 <trex005> Hello all, I'm trying to get a scroller to function inside a onyx.popup and can't get it to work.  Can anyone help me out? http://jsfiddle.net/trex005/2oj805by/
Oct 07 17:47:46 <trex005> what it does is let my content go outside the popup, and cause a scroller on the outside of the app to trigger.
Oct 07 17:48:49 <trex005> Let me add, I can make it work with CSS width and height,
Oct 07 17:49:11 <trex005> but in my app, I need it on only one portion of the popup, so I want to use fit
Oct 07 17:49:44 <dmanderson> here you go trex005 http://jsfiddle.net/2oj805by/1/
Oct 07 17:50:45 <trex005> I might have to use fittable rows.... :)
Oct 07 17:51:00 <trex005> Duh I just was not thinking through
Oct 07 18:02:41 <GodGinrai> Hey dmanderson, this rule is screwing things up for me:
Oct 07 18:02:47 <GodGinrai> .enyo-fittable-columns-layout.enyo-stretch > * {
Oct 07 18:02:51 <GodGinrai> height: 100%;
Oct 07 18:02:52 <GodGinrai> }
Oct 07 18:03:53 <GodGinrai> wait nvm
Oct 07 18:03:55 <GodGinrai> no it isn't
Oct 07 18:03:56 <GodGinrai> god
Oct 07 18:04:02 <GodGinrai> I don't understand why this is doing this -_-
Oct 07 18:04:27 <GodGinrai> I don't see any CSS rules that are making this fittablecolumns greedily take the height -_-
Oct 07 18:06:27 <GodGinrai> also, the inspector says that the height of the element within it (which has a height of 100%) is a higher computed value than the element itself....
Oct 07 18:18:29 <GodGinrai> dmanderson: Can you test the code in this fiddle locally and see if it still displays correctly? http://jsfiddle.net/ma7txgtr/
Oct 07 18:18:36 <GodGinrai> Because it does not work for me locally
Oct 07 18:18:41 <GodGinrai> And I can't figure out why
Oct 07 18:19:32 <Semanticfire> dmanderson, any update on the sizing issue ?
Oct 07 18:19:33 <dmanderson> looks ok? http://imgur.com/03LBeLP
Oct 07 18:20:07 <dmanderson> I’ve started looking Semanticfire, just haven’t had a lot of time to dig into it
Oct 07 18:20:12 <Semanticfire> okay :-/
Oct 07 18:20:19 <dmanderson> :D
Oct 07 18:21:06 <GodGinrai> dmanderson: that's in a fiddle
Oct 07 18:21:15 <GodGinrai> I said that the fiddle doesn't exhibit the problem
Oct 07 18:21:30 <GodGinrai> but that when that code is ran on its own locally, the problem appears
Oct 07 18:23:24 <dmanderson> Ah sorry GodGinrai, let me check
Oct 07 18:24:27 <dmanderson> looks fine locally as well under Chrome 37
Oct 07 18:24:47 <dmanderson> FF and Safari both good as well.
Oct 07 18:24:54 <GodGinrai> :\
Oct 07 18:25:01 <GodGinrai> Both FF and Chrome don't display it correctly here
Oct 07 18:27:59 <GodGinrai> dmanderson: and you didn't add any other code?
Oct 07 18:29:29 <dmanderson> Nope, just dumped it into a boilerplate
Oct 07 18:30:26 <Garfonso> hi all
Oct 07 18:30:28 <GodGinrai> try with the latest nightly
Oct 07 18:30:31 <GodGinrai> hey Garfonso
Oct 07 18:31:12 <Garfonso> is there a way for a control to find out which part of it is visible, i.e. if it is inside a scroller?
Oct 07 18:31:45 <GodGinrai> dmanderson: Also, you're seeing the inputs, "chart goes here", and fotter?
Oct 07 18:31:47 <GodGinrai> *footer
Oct 07 18:32:02 <GodGinrai> Garfonso: which part of it?
Oct 07 18:33:36 <Garfonso> I have a big control, like 1000x1000 inside a scroller and on a smaller screen, like 800x800 I'd need to know which part is visible inside the scroller. Is there a way to know that inside the child control?
Oct 07 18:33:49 <Garfonso> of course the scroller knows that and I know how to get that from the scroller.
Oct 07 18:33:54 <dmanderson> Yup, I am using using the latest merges in master
Oct 07 18:34:21 <GodGinrai> dmanderson: Because IE11 displays it correctly, but Chromium 38 and Firefox 32 do not
Oct 07 18:34:27 <GodGinrai> for me
Oct 07 18:34:44 <dmanderson> Hrm
Oct 07 18:35:25 <dmanderson> Garfonso you can the bounds of the control to see if it is in the view port
Oct 07 18:37:05 <GodGinrai> dmanderson: http://imgbin.org/index.php?page=image&id=19647
Oct 07 18:37:07 <GodGinrai> see?
Oct 07 18:37:35 <dmanderson> Yeah that’s broke.
Oct 07 18:38:38 <GodGinrai> You're absolutely sure you aren't using any alternative code?
Oct 07 18:41:28 <dmanderson> Yup positive
Oct 07 18:41:36 <dmanderson> Latest pulls for each master
Oct 07 18:41:36 <GodGinrai> ugh
Oct 07 18:41:51 <GodGinrai> I don't understand why this is happening -_-
Oct 07 18:41:51 <dmanderson> I’m on OSX though
Oct 07 18:41:56 <dmanderson> Wonder if its a windows thing.
Oct 07 18:42:20 <GodGinrai> Well, like I said, IE11 renders it properly, while 2 other browsers do not
Oct 07 18:42:32 <dmanderson> Yeah, it’s not uncommon for OS’s to have browser quirks.
Oct 07 18:42:35 <GodGinrai> plus, those 2 browsers render the result in the fiddle correctly
Oct 07 18:42:51 <dmanderson> Some linux versions don’t support accelerated compositing, and so things just don’t work.
Oct 07 18:45:47 <GodGinrai> When I disable the "height: 100%" rule, it works correctly
Oct 07 18:45:55 <GodGinrai> but that rule shouldn't be the problem
Oct 07 18:46:13 <GodGinrai> since it is on inside divs, not the container div... :\
Oct 07 18:46:38 * GodGinrai wishes firebug could diff css rules between elements on 2 pages
Oct 07 18:50:02 <Garfonso> dmanderson: how to get the viewport? *scratches head*
Oct 07 18:52:43 <GodGinrai> Garfonso: http://stackoverflow.com/questions/123999/how-to-tell-if-a-dom-element-is-visible-in-the-current-viewport
Oct 07 18:54:31 <dmanderson> Thanks GodGinrai!
Oct 07 18:57:58 <GodGinrai> dmanderson: you can thank me by figuring out what's causing this magical bug in my code :P
Oct 07 18:58:08 <dmanderson> :D
Oct 07 19:09:52 <Garfonso> that helps, thanks a lot. :)
Oct 07 19:10:10 <GodGinrai> yw
Oct 07 19:11:30 <Garfonso> yeah.. with that I fixed webos-lib/webview to work on webOS 2.x (i.e. the phones). :)
Oct 07 19:12:05 <GodGinrai> Garfonso: nice.  Why did it need that to work on the phones?
Oct 07 19:14:14 <Garfonso> because.. uhm.. it is based on the enyo 1.0 webview component which only worked on the TouchPad... on the phones the "browser adapter" thingie worked a bit different and needed some fixes... For example somehow you need to reroute clicks to a special function. But also scrolling was an issue
Oct 07 19:15:38 <GodGinrai> And so you needed to check to make sure the things you were clicking on were visible in the webview so that when you clicked outside of it you weren't activating things in the webview?
Oct 07 19:17:19 <Garfonso> no, I need to calculate where the user clicked on in the coordinates of the webpage that the webview shows, but which might not be 100% visible.
Oct 07 19:17:32 <Garfonso> because I moved the scroller around the webview.
Oct 07 19:17:56 <GodGinrai> ah
Oct 07 19:18:17 <Garfonso> might not be the best solution, but works. At least for the usual oauth usecase.
Oct 07 19:19:51 <GodGinrai> I see
Oct 07 19:31:36 <Garfonso> hm.. somehow scroller & popup seems to be a problematic combination
Oct 07 19:39:30 <Garfonso> at least on this legacy webkit engine on the webos phones.. :-(
**** ENDING LOGGING AT Wed Oct 08 03:00:00 2014