There are levels of expertise, even as a senior developer.
I expect a full-stack senior developer to be able to lift a webapp from scratch (frankly I'll probably expect it even from an experienced junior full-stack developer in today's PaSS world).
I expect every full-stack senior developer to be able to get the job done in both front-end features and back-end features, as long as they aren't very specific. I expect him to be able to do so in a maintainable and relatively performant way that has structure and consistency behind it.
I expect him to know best practices for both front-end and back-end. In front-end that is for instance knowing that you don't measure dom elements inside animations.
I don't expect him to know the internals that led to these best practices (in this case how the browser works and the nature of the layout phase) nor when is it ok to break them.
If best practices were followed but something still doesn't work it's okay to call an expert (for instance an expert on browser performance).
Specializing as a fullstack-developer means that you are also an expert in some field (for instance browser performance, or web animations, or graphs).
Perhaps a better phrasing is that since I don't really expect pure front-end senior developers to know it either, only those who specialize in certain fields, so really a full-stack developer is already a senior front-end developer and a senior back-end developer.
There isn't something that makes a front-end developer more specialized in front-end then a full-stack developer, it's just that he didn't work enough on back-end.
I expect a full-stack senior developer to be able to lift a webapp from scratch (frankly I'll probably expect it even from an experienced junior full-stack developer in today's PaSS world). I expect every full-stack senior developer to be able to get the job done in both front-end features and back-end features, as long as they aren't very specific. I expect him to be able to do so in a maintainable and relatively performant way that has structure and consistency behind it.
I expect him to know best practices for both front-end and back-end. In front-end that is for instance knowing that you don't measure dom elements inside animations.
I don't expect him to know the internals that led to these best practices (in this case how the browser works and the nature of the layout phase) nor when is it ok to break them. If best practices were followed but something still doesn't work it's okay to call an expert (for instance an expert on browser performance).
Specializing as a fullstack-developer means that you are also an expert in some field (for instance browser performance, or web animations, or graphs).
Perhaps a better phrasing is that since I don't really expect pure front-end senior developers to know it either, only those who specialize in certain fields, so really a full-stack developer is already a senior front-end developer and a senior back-end developer.
There isn't something that makes a front-end developer more specialized in front-end then a full-stack developer, it's just that he didn't work enough on back-end.