Wow, thanks a lot, looks great. The angular way. I am studying it now.
On Thu, Jan 23, 2014 at 9:15 AM, Sander Elias sanderel...@gmail.com wrote:
Olivier,
I gave it a shot: http://plnkr.co/edit/FZrpU4?p=preview
--
You received this message because you are subscribed to the Google Groups
Just a partial auto-response, for future reference.
currentTarget is null if Firefox is used.
To make sure it is cross-browser, this is what is needed:
var el = event.target || event.srcElement;
On Wed, Jan 22, 2014 at 4:25 PM, Olivier Percebois-Garve
perceb...@gmail.com wrote:
Hi Sander,
hummm...
var el = $event.target || $event.srcElement;
On Thu, Jan 23, 2014 at 11:38 AM, Olivier Percebois-Garve
perceb...@gmail.com wrote:
Just a partial auto-response, for future reference.
currentTarget is null if Firefox is used.
To make sure it is cross-browser, this is what is
Hi Sander,
I am currently playing with it and trying to let my mind be changed, before
to comment on it.
What would be a better way to read the data ?
(The directive is meant to be used by other dev, I thought I would be nice
to just have to tell them code a normal select element, with only a few
Olivier,
Put it in a array on the scope, and iterate.
in the controller:
$scope.items = [
{value : 1 , description : 'Hello darkness,'},
{value : 2 , description : 'my old friend'},
{value : 3 , description : 'I'v come to talk with you again.'},
{value : 4 , description
Hi Olivier,
You are right, if you click on an element, that you removed from the dom,
then added, then removed again, and then added again, somehow the browser
lost track of its parent!
I'm not sure where to even begin on this one! I'm not even sure if it's an
angular or a browser issue.
Hi Olivier,
You are right, it is just taken out once, and then put back in.
I didn't scan your code carefully enough. After using the tidy-up button it
became more apparent!
Will go over it once more, and let you know. Probably not today anymore!
Regards
Sander
--
You received this message
Oh, do you mind sharing your working plunk? perhaps its of use for anybody
else!
On Wednesday, January 22, 2014 6:13:28 PM UTC+1, Sander Elias wrote:
Hi Olivier,
Thanks for the update. I was indeed thrown off by all the cruft.
Apparently so was the browser/angular ;)
Regards
Sander
Sure http://plnkr.co/edit/VgGVJO?p=preview
its even annoted for you pointing to the bug that doesn't exist anymore ;).
I'd love comment about the coding style though and my crimes against the
angularish aesthetics...
On Wed, Jan 22, 2014 at 6:14 PM, Sander Elias sanderel...@gmail.com wrote:
Hi Olivier,
I don't have the steam to work it out now, But why did you do the entire
construct like that it looks overly complicated and fragile to me?
Don't see a reason for the transclude.
How about splitting it in 2?
1 dropdown directive, that hold the logic for the list, and the
Hi Sander,
If you need to rest please do it we can continue this conversation
another day.
The reason for the transclude is the replaceWith of the base element of the
directive. The directive replace the custom element dropdown with valid
markup.
I thought that was pretty the point of
Hi Olivier,
I will go over your reply and answer inline.
The reason for the transclude is the replaceWith of the base element of the
directive. The directive replace the custom element dropdown with valid
markup.
I thought that was pretty the point of angularjs, i.e the ability to
12 matches
Mail list logo