View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
09115 | Bug reports | Survey taking | public | 2014-06-24 15:47 | 2014-07-30 16:18 |
Reporter | ronny_todgers | Assigned To | c_schmitz | ||
Priority | normal | Severity | minor | ||
Status | closed | Resolution | fixed | ||
Product Version | 2.05+ | ||||
Fixed in Version | 2.05+ | ||||
Summary | 09115: Chrome has a bug which causes slider layouts not to be styled properly after the doNumericSlider function is called | ||||
Description | Summary says it all really: styles applied to slider layouts are not properly applied to the slider itself after the doNumericSlider function is called when using Chrome - works fine on other browsers. | ||||
Steps To Reproduce | Create a multi-numeric question - set it to be in slider format - create some custom styling such as : .slider-label{display:block !important;text-align:center !important;float:none !important;width:100% !important; margin: 20px 0 0px;} In Chrome the slider is drawn at a fixed width rather than the specified 50% - in firefox it is fine. This seems to be an established bug in chrome (http://stackoverflow.com/questions/3485365/how-can-i-force-webkit-to-redraw-repaint-to-propagate-style-changes) We need a work around in limesurvey - the best I can come up with is adding this to the end of the doNumericSlider function - it works a treat and perhaps should be included in the main source so I don't have to patch on upgrade? //fix buggy chrome which doesn't properly apply the css rules after this insertion | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | 140422 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | Chrome | ||||
Database type & version | Postgres 9.1.13 | ||||
Server OS (if known) | Debian 7.4 | ||||
Webserver software & version (if known) | Apache/2.2.22 | ||||
PHP Version | Version 5.4.4-14+deb7u9 | ||||
Note that while this is a bug in Chrome not Limesurvey it is years old and clearly unlikely to get fixed anytime soon so it would (in my mind) make sense to put an effectively zero cost workaround in place. |
|
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=14341 |
|
Thank you! |
|
2.05+ Build 140730 released |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2014-06-24 15:47 | ronny_todgers | New Issue | |
2014-06-24 15:47 | ronny_todgers | File Added: limesurvey_survey_642721.lss | |
2014-06-24 15:54 | ronny_todgers | Note Added: 30222 | |
2014-07-25 09:23 | c_schmitz | Assigned To | => c_schmitz |
2014-07-25 09:23 | c_schmitz | Status | new => assigned |
2014-07-25 09:24 | c_schmitz | Changeset attached | => LimeSurvey master 9767c0ff |
2014-07-25 09:24 | c_schmitz | Note Added: 30346 | |
2014-07-25 09:24 | c_schmitz | Resolution | open => fixed |
2014-07-25 09:24 | c_schmitz | Note Added: 30347 | |
2014-07-25 09:24 | c_schmitz | Status | assigned => resolved |
2014-07-25 09:24 | c_schmitz | Fixed in Version | => 2.05+ |
2014-07-30 16:18 | c_schmitz | Note Added: 30373 | |
2014-07-30 16:18 | c_schmitz | Status | resolved => closed |