mike-north/ember-cli-materialize

[Bug] Select doesn't tear its self down completely

Open

#86 opened on Apr 24, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (305 stars) (117 forks)batch import
bugfixed in materialize-v1.0.0help wantedv0

Description

The following code in the {{md-select}} component registers some listeners when the Materialize javascript is called

this.$('select').material_select();

Anything registered by this code needs to be cleaned up in the component's willDestroyElement hook

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Ember.js component lifecycleJavaScript event handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the select component file (likely app/components/md select.js or addon/components/md select.js) to identify all listeners registered by material select(). Then implement the cleanup in the willDestroyElement hook. Check if Materialize provides a method to tear down the select plugin (e.g., material select('destroy')). Also review other Materialize components in the project for patterns of proper teardown.