5 ms·
Create a modular UI framework that allows modules to import their own stylesheets. You hit this problem really quickly.
by n8agrin 17y ago
Create a modular UI framework that allows modules to import their own stylesheets. You hit this problem really quickly.
- deleted 17y ago[deleted]
- deleted 17y ago[deleted]
- qeorge 17y agoPerhaps, but if you're including 30+ stylesheets in a given page you're doing it wrong. Every stylesheet is an extra (blocking) HTTP request. 5 is already too many, but 30 is seriously impacting your user's experience.
- DrJokepu 17y agoThis bug can be triggered by inline stylesheets as well which do not create additional HTTP requests.
- qeorge 17y agoFair point, but in what case does including 30 inline stylesheets make sense? I'm hesitant to call this a bug.
- pavs 17y agoWell, with MS, its a feature.
- dkarl 17y agoAt MS, it might be dictated by a coding standard. More seriously, I was once treated VERY skeptically by an old-school programmer (not at MS, never worked there) when I replaced some of his fixed-sized buffers with resizeable ones. "If our customers are running workloads that create more than 256 frooble node objects, I want to hear about it." Via a bug report? Really? And then get a new bug report next year when the new limit is reached? But he was adamant, and if it was up to him we wouldn't have made the change at all. The way he worked, you knew how many frooble node objects the customer needed, and if you were wrong then you fixed the code.
- pyre 17y agoIf it was meant to be a feature, it should have at least been documented. How is it good to have undocumented, arbitrary limitations on a platform that you are using?
- knuckle_cake 17y agoThe one time I've run into this 'bug' in the past was on a site that used lots of javascript plugins, more and more of which are coming with their own CSS files nowadays. Of course you can concat them together, but that adds a maintenance burden in the future whose size can vary wildly. At the very least, there is a documentation bug here. The reason for this seemingly arbitrary limit should be documented by MS.
- jey 17y agoIt makes perfect sense if you're generating your HTML and CSS from some kind of code-generator. Limiting it to only 30 style tags is really arbitrary and small.
- daleharvey 17y agousing inline style tags directly after elements can have a noticeable speedup on a pages rendering, dynamically generated pages could quite easily have well over 30 with the only downside being this silly limit. and that isnt mentioning the boundary situations for things like web page builders with the ability to user define styles in which having a "lot" of style tags is architecturally a good idea. I am quite tired of this "your doing it wrong" meme when its used instead of "you arent doing the same thing I am doing"
- ubernostrum 17y agoIt's not unheard-of for components on a page to be separately generated, and for each to emit its own HTML and style info.
- deleted 17y ago[deleted]
- thenduks 17y agoTwo words: development mode
- jeroen 17y agoI'd hope there would be server side combining of stylesheets. I have seen performance suffer from including about 10 stylesheets; don't want to imagine 30+.
- deleted 17y ago[deleted]
- mikeryan 17y agoIn the reddit thread this seemed to crop up a lot in Drupal where each module installed can use its own CSS sheet. There's apparently a setting to merge them but at least in that case something like this issue cropping up makes sense.
- Semiapies 17y agoOK, I suspected that. I think that's a code smell, though; I have trouble seeing why you wouldn't want to get such styles into the main stylesheet.